On Fri, 2009-01-30 at 20:21 -0500, milosz wrote:
> hi all,
>
> anyone else having this issue with snom m3 transfers and the patton
> gateways? transfers from the snoms to other phones calls are failling
> with 403's for incoming calls only.
>
> including a trace, can't really tell what the problem is.
The problem is that your Snom phone is not correctly processing the
Record-Route inserted by the sipXecs proxy.
In the initial INVITE received by the phone, the proxy has inserted a
Record-Route header:
INVITE sip:[email protected] SIP/2.0
Record-Route:
<sip:192.168.3.19:5060;lr;sipXecs-rs=%2Afrom%7EYzc2YThmMmUyNjk3OWI5.400_authrules%2Aauth%7E%21915d2cc3966c8d33d4392e65d567b325>
But the Route that the phone is using has stripped the sipXecs-rs
parameter from the route URL - see the 200 OK response to that INVITE:
INVITE sip:[email protected] SIP/2.0
Route: <sip:192.168.3.19;lr>
modifying the route set like that is incorrect behavior. In this case,
what the phone has done is removed the information the proxy would have
used to authenticate subsequent requests within the call; the lack of
that parameter causes authentication failures that prevent your
transfer.
I suggest checking with Snom to see if there is newer firmware for your
phone that does this correctly.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
