[Spce-user] Peer routing

[John Murray]

Jon thanks.

Looking at http://www.kamailio.org/docs/modules/3.3.x/modules/lcr.html#id2547463

" A tuple can be marked as a "stopper" tuple. If a "stopper" tuple matches, then matching stops at it and all other tuples with shorter prefixes are not considered."

Maybe this could do it? I'll try this and get back to you. I guess it should be easy to add it to the web interface as an option if it works.

Regards

John

-----Original Message-----
From: spce-user-bounces at lists.sipwise.com [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of Jon Bonilla (Manwe)
Sent: 15 November 2012 20:49
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Peer routing

El Thu, 15 Nov 2012 20:28:23 -0000
"John Murray" <john.murray at skyracktelecom.com> escribió:

> Hello,
> 
>  
> 
> I have a PSTN peer group with multiple peering servers for inbound and 
> outbound traffic. I have a default route pointing to these servers.
> 
>  
> 
> I have a asterisk box configured in another peering group as a peering 
> server and a rule with a prefix pointing at it (eg. 447729 ).
> 
>  
> 
> Calls from the PSTN are routed to this asterisk box however this box 
> occasionally gives '500 Service Unavailable' which causes SPCE to 
> route the call back out my default PSTN peer which wants to send it back again etc.
> 
>  
> 
> Can I build a rule that says route this prefix here and only here?
> 
>  


Would be a nice to have feature. At the moment what you could do is to make the default peering rule not match with 447729 instead of leaving a blank one.

You could use a negative rule using the callee_pattern (instead of
callee_prefix) that matches everything except that prefix(?)