I don't have a lot of information here, so I can't get to the bottom of
the problem, but the outline is this:
I did "merge-logs --containing=7f00000113ce000b7150000bb418" to isolate
the call-id that analyze_483s found. What I see is that the INVITE is
sent from 123.102.12.9:5060 to the proxy. At that point, the INVITE has
these vital fields:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 123.102.12.9:5060;branch=z9hG4bKv40hu430bof1deomt6o0.1
Route: <sip:0286681...@x-on2abuacn1hs01-20:5060;lr>
Max-Forwards: 70
Although the request-URI gives the address of the proxy, there is a
Route header, which must be obeyed first. It gives the address
"X-0N2ABUACN1HS01-20:5060". I have no idea what that is, but apparently
DNS resolves it to 123.102.12.9, and the proxy sends the INVITE there.
The next thing I see is the INVITE being returned from 123.102.12.9.
Normally I would expect this, as that is the address in the request-URI,
but the Route header has not been removed (like it should be). So the
proxy obeys the Route header and sends the request back to 123.102.12.9.
This continues, with 123.102.12.9 never removing the Route header, until
Max-Forwards counts down to 0.
Dale
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
