[Spce-user] Peer gateway returning a wrong response

[Marco Capetta]

Hi Raul,

you can try adding the code to "kamailio.proxy.filter_failover_response" 
params of config.yml file.
The drawback is that the configuration will be system wide, so it iwll 
be applied automatically to all the peers.


Regards
Marco

On 2/13/20 12:08 AM, Raúl Alexis Betancor Santana wrote:
> Hi all,
>
> We a facing the problem with one carrier, that returns a "404 
> not-found" for calls routed throught them that the number was before 
> on their network but now have been ported out, It's a problem inside 
> their internal LPN service, but they take too much time to solving it 
> each time whe open a ticket with them so we need to translate that 404 
> into any response code that SPCE will undestand as "Try other gateway".
>
> Are the "SIP Response Codes", inside Peering Groups -> [group] -> 
> Peering Server -> [peer server] -> Preferences  for this ?, if not, is 
> ther any option on SPCE for doing this without having to go to the 
> routing script and do a hand-modification of the template ?
>
> I'm testing under a mr7.5.2
>
> Best regards.
>

-- 
*Marco Capetta *
VoIP Developer

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2044 <tel:+4313012044>
Email: mcapetta at sipwise.com <mailto:mcapetta at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200213/d73e80f2/attachment-0002.html>