SIP wrote:
Right. That's the part that's difficult to discover. Where the problem lies.
The INVITE gets there correctly... I see the path.
UA ---> INVITE 1101201 ---> other proxy ---> INVITE 201 ---> our proxy:5060 ---> INVITE 201 ---> our proxy:5090 ---> 200 OK
The ACK, however, takes a slightly different path:
other proxy ---> ACK 201 ---> our proxy:5060 ---> ACK 201 ---> our proxy:5060 ---> rinse ---> repeat
However, from locally registered clients, the path is:
UA ---> ACK 201 ---> our proxy:5060 ---> ACK 201 ---> our proxy:5090 ---> life is good.
It's the whole discrepancy that throws me. I mean... the SIP messages are, for all intents and purposes, going through the same config. I can't figure out why one client would not experience the same issues as any other client, locally registered or not.
The Contact header response from the INVITE is correct:
Contact: sip:201@63.64.65.66:5090.
Look at the Contact Header inside the 200 OK message when the call is answered by SEMS and follow it through all the way to the remote end. This is the key piece of information that tells the remote end where to send the ACK. If it is indeed at port 5090 then the remote end must generate an: ACK sip:201@63.64.65.66:5090.
Andres, http://www.telesip.net