[Freeswitch-users] FreeSwitch Sending NOTIFY to incorrect port based on SUBSCRIBE request over UDP

[Parfitt, Stephen]

Hi All,

I've been doing some testing against FreeSwitch 1.2.0 and noticed what
looks like a bug.

root at Freeswitch> version

FreeSWITCH Version
1.2.0-rc2+git~20120616T193227Z~068586f28f+unclean~20120618T093505Z


192.168.8.238 = Freeswitch
192.168.8.168 = proxyhost.test.net


A Client sends the following SUBSCRIBE to freeswitch


SUBSCRIBE sip:2001 at proxyhost.test.net SIP/2.0
Call-ID: 2039516157894306129 at 192.168.8.168
Via: SIP/2.0/UDP 192.168.8.168:5070;branch=z9hG4bKC0A808A82E8652DB03
Via: SIP/2.0/UDP 192.168.8.168:5070;branch=z9hG4bKC0A808A82E8652DB11
To: sip:2001 at proxyhost.test.net
CSeq: 1 SUBSCRIBE
Contact: <sip:proxyhost.test.net:5060>
From: sip:2001 at proxyhost.test.net
;tag=1297284766*476741369860*990463165~476741369860~fmc.sar~
Content-Length: 0
Expires: 3600
Event: message-summary
Accept: application/simple-message-summary
Route: <sip:192.168.8.238;lr>
Max-Forwards: 69


FreeSwitch responds with:


SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 192.168.8.168:5070;branch=z9hG4bKC0A808A82E8652DB03
Via: SIP/2.0/UDP 192.168.8.168:5070;branch=z9hG4bKC0A808A82E8652DB11
From: <sip:2001 at proxyhost.test.net
>;tag=1297284766*476741369860*990463165~476741369860~fmc.sar~
To: <sip:2001 at proxyhost.test.net>;tag=9t8fu6DedmnQ
Call-ID: 2039516157894306129 at 192.168.8.168
CSeq: 1 SUBSCRIBE
Contact: <sip:2001 at 192.168.8.238:5060>
Expires: 3600
User-Agent:
FreeSWITCH-mod_sofia/1.2.0-rc2+git~20120616T193227Z~068586f28f+unclean~20120618T093505Z
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Allow-Events: talk, hold, presence, dialog, line-seize, call-info, sla,
include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=3600
Content-Length: 0

So I would expect subsequent NOTIFY messages to be send to the address &
port in the contact: sip: proxyhost.test.net:5060 (contact header from
SUBSCRIBE)

However I do not see the NOTIFY requests arrive at sip:proxyhost.test.net on
port 5060, a wireshark trace on FreeSwitch says is sending them to a
different port, port 33406 which is the port Freeswitch received the
request on.


This is how the packet looks in WireShark:

Ethernet II, Src: 42:61:a8:ef:c3:de (42:61:a8:ef:c3:de), Dst:
96:cd:bb:a4:a4:2e (96:cd:bb:a4:a4:2e)
Internet Protocol Version 4, Src: 192.168.8.238 (192.168.8.238), Dst:
192.168.8.168 (192.168.8.168)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 34406 (34406)
 **Would expect this to be 5060**
Request-Line: NOTIFY sip:proxyhost.test.net:5060 SIP/2.0

I thought this defect might be in the ball park:

http://jira.freeswitch.org/browse/FS-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel


Anyone seen this?

To resolve I used TCP instead of UDP but wanted to flag it up to see if
anyone else had seen it


Regards

Steve P

 
--------------------
Note: The information contained in this message may be privileged and confidential 
and protected from disclosure. If the reader of this message is not the intended 
recipient, or an employee or agent responsible for delivering this message to the 
intended recipient, you are hereby notified that any dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify us immediately by replying to the message and 
deleting it from your computer. Thank you. Thrupoint, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20120627/5efb3466/attachment.html