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