Hi,
rport missing is no problem at all, default 5060 is then used. The branch=0 in the ACK might be the problem (if Cisco does not match it with the INVITE (but then it should retransmit the 200 OK reply)).
You can try add syn_branch=0 to the ser.cfg to have the branch id calculated for ACKs too.
Michal
On Wed, 2007-02-07 at 13:02 +0900, Sahria Hao wrote:
I got an additional SIP message log from my 5300.
Scenario:
[UA] => [Asterisk] => [SER] => [CISCO AS5300] => [PSTN]
[UA] "12" [Asterisk] 0355558888@MY.ASTERISK.IP.ADDRESS [SER] MY.SER.IP.ADDRESS [CISCO AS5300] MY.AS5300.IP.ADDRESS [PSTN] T1 Line
And maybe I found little bad Via header in ACK message from Asterisk (via SER) to AS5300.
Feb 7 03:22:34.401: Received: ACK sip:056708077771111@MY.AS5300.IP.ADDRESS:5060 SIP/2.0 Record-Route: sip:MY.SER.IP.ADDRESS;ftag=as2ad98fe4;lr Via: SIP/2.0/UDP MY.SER.IP.ADDRESS;branch=0 Via: SIP/2.0/UDP MY.ASTERISK.IP.ADDRESS:5060;branch=z9hG4bK0a0daaf9;rport=5060 ...
Why Via header looks like no branch value and port value...? And all SIP messages have no Route header.
I attached AS5300 SIP message log (see below).
Any ideas?
Sahria