They probably shouldn't be responding 484 to them... hrm /b On Jul 14, 2009, at 4:07 AM, Andy wrote:
Hi Anthony,
Thanks for your reply. The trace of the ping request looks like this. Any clues?
send 674 bytes to udp/[77.240.48.94]:5060 at 09:07:25.479313:
------------------------------------------------------------------------ OPTIONS sip:voiptalk.org;transport=udp SIP/2.0 Via: SIP/2.0/UDP 77.86.49.249;rport;branch=z9hG4bK8rBQ4a33Ny02K Max-Forwards: 70 From: <sip:77.86.49.249>;tag=a8U21NNZ23tBB To: <sip:voiptalk.org> Call-ID: 96da25e1-eaf8-122c-02ae-0019d15ec7e1 CSeq: 117662779 OPTIONS Contact: <sip:mod_sofia@77.86.49.249:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-13850 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO, PUBLISH Supported: timer, precondition, path, replaces Allow-Events: talk, presence, dialog, call-info, sla, include- session-description, presence.winfo, message-summary, refer Content-Length: 0
------------------------------------------------------------------------ recv 352 bytes from udp/[77.240.48.94]:5060 at 09:07:25.486124:
------------------------------------------------------------------------ SIP/2.0 484 Address Incomplete Via: SIP/2.0/UDP 77.86.49.249;rport=5060;branch=z9hG4bK8rBQ4a33Ny02K From: <sip:77.86.49.249>;tag=a8U21NNZ23tBB To: <sip:voiptalk.org>;tag=fd79486175647ed1617969929fdaad02.f21c Call-ID: 96da25e1-eaf8-122c-02ae-0019d15ec7e1 CSeq: 117662779 OPTIONS Server: OpenSIPS (1.5.1-notls (x86_64/linux)) Content-Length: 0
------------------------------------------------------------------------ 2009-07-14 10:07:25.483507 [WARNING] sofia.c:2810 Ping failed voiptalk.org 2009-07-14 10:07:25.483507 [WARNING] sofia.c:2813 Unregister voiptalk.org
Andy