Hello List. I'm still stuck with this problem. I really don't know if it is a configuration problem or maybe a problem with SER, i was hopping that someone could help me. I have a NAT'd client, when this client make a call, and before the called party answer the call the call is canceled, I see a "200 - Cancelling" message coming from SER to my NAT'd client. All the previus messages goes to the correct port informed in the rport, but this 200-Cancelling message goes to port 5060, so the message didn't reach the endpooint. It this a problem with the configuration or a problem with SER?. Here is SIp debug for the final CANCEL message.
U xx.xx.148.244:64435 -> xx.xx.154.35:5060 CANCEL sip:2408196@sipproxy.mydomain.com SIP/2.0 Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bK2542303ca430 From: sip:5555848110@sipproxy.mydomain.com;tag=2542303ca4 To: sip:2408196@sipproxy.mydomain.com Call-ID: 252eb142-ae30-30f0-803c-0002a400f1e9@192.168.0.191 CSeq: 30 CANCEL Date: Thu, 16 Jun 2005 07:45:57 GMT User-Agent: AddPac SIP Gateway Content-Length: 0 Max-Forwards: 70
# U xx.xx.154.35:5060 -> xx.xx.148.231:5060 CANCEL sip:7072408196@xx.xx.148.231:5060 SIP/2.0 Record-Route: sip:2408196@xx.xx.154.35;ftag=2542303ca4;lr=on Via: SIP/2.0/UDP xx.xx.154.35;branch=z9hG4bKe6c7.e2501f15.0 Via: SIP/2.0/UDP 192.168.0.191:5060;received=xx.xx.148.244;branch=z9hG4bK2542303ca430 From: sip:5555848110@sipproxy.mydomain.com;tag=2542303ca4 To: sip:2408196@sipproxy.mydomain.com Call-ID: 252eb142-ae30-30f0-803c-0002a400f1e9@192.168.0.191 CSeq: 30 CANCEL Date: Thu, 16 Jun 2005 07:45:57 GMT User-Agent: AddPac SIP Gateway Content-Length: 0 Max-Forwards: 69 P-hint: H323-Side
# U xx.xx.154.35:5060 -> xx.xx.148.244:5060 SIP/2.0 200 cancelling Via: SIP/2.0/UDP 192.168.0.191:5060;branch=z9hG4bK2542303ca430;received=xx.xx.148.244 From: sip:5555848110@sipproxy.mydomain.com;tag=2542303ca4 To: sip:2408196@sipproxy.mydomain.com;tag=8acf748d21b6bc66e44e951325ba3f1c-b28 c Call-ID: 252eb142-ae30-30f0-803c-0002a400f1e9@192.168.0.191 CSeq: 30 CANCEL Server: Sip EXpress router (0.8.14-3 (i386/linux)) Content-Length: 0 Warning: 392 xx.xx.154.35:5060 "Noisy feedback tells: pid=23757 req_src_ip=xx.xx.148.244 req_src_port=64435 in_uri=sip:2408196@sipproxy.mydomain.com out_uri=sip:7072408196@xx.xx.148.231:5060 via_cnt==1"
This cause a endless CANCEL message flow coming from my endpoint.
Hope that someone can help me here Thanks in advance Best Regards
Ricardo Martinez
On Nov 11, 2004 at 12:52, Ricardo Martinez rmartinez@redvoiss.net wrote:
Hello List. I'm still stuck with this problem. I really don't know if it is a configuration problem or maybe a problem with SER, i was hopping that someone could help me. I have a NAT'd client, when this client make a call, and before the called party answer the call the call is canceled, I see a "200 - Cancelling" message coming from SER to my NAT'd client. All the previus messages goes to the correct port informed in the rport, but this 200-Cancelling message goes to port 5060, so the message didn't reach the endpooint.
All the replies to a request are supposed to go to the rport. CANCEL is a different request. CANCEL will go to its request uri , in your case sip:2408196@sipproxy.mydomain.com.
It this a problem with the configuration or a problem with SER?. Here is SIp debug for the final CANCEL message.
A nat-config problem probably. Do you use nathelper? Do you use fix_nated_contact() for REGISTERs comming from natted UAs?
Andrei
-
Andrei Pelinescu-Onciul -
Ricardo Martinez