[Spce-user] Initial Loose-Routing Forbidden
John Murray
john.murray at skyracktelecom.com
Mon Jun 4 06:24:03 EDT 2012
Thanks,
The Route header points to a slightly different domain which I have now
added and this works.
The provider has 2 gateways so perhaps the route header is to define which
one is used.
We have holiday until Wednesday in the UK so I will check with them then.
Best regards
John
-----Original Message-----
From: Andrew Pogrebennyk [mailto:apogrebennyk at sipwise.com]
Sent: 04 June 2012 10:29
To: Klaus Darilion
Cc: John Murray; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Initial Loose-Routing Forbidden
Hi!
On 06/04/2012 11:11 AM, Klaus Darilion wrote:
> Probably your clients send out-of-dialog requests with Route headers.
>
> Regarding SPCE: Wouldn't it be more reliable to just ignore and remove
> Route headers on incoming out-of-dialog requests?
That's what we do when Route header on incoming out-of-dialog requests
points to one of our domains, i.e.:
if(loose_route())
{
...
if(!has_totag())
{
if($du != $null && is_domain_local("$dd"))
{
xlog("L_INFO", "Reset initial local route -
M=$rm R=$ru F=$fu T=$tu
IP=$avp(s:ip):$avp(s:port) ($si:$sp) ID=$ci\n");
$du = $null;
}
...
If the initial Route header points to somewhere else we reject it, for
security reasons I believe.
John, could you check with the peer why it's sending Route in initial
INVITE?
BR,
Andrew
More information about the Spce-user
mailing list