[SIP Beyond VoIP] Sylk does not use maddr in the 200 OK that is reply to NOTIFY request
recordroute at gmail.com
Wed Jan 30 23:40:40 CET 2013
My Sip Proxy keeps client's IP in the Contact header of 200 OK to reply to
NOTIFY request and adds its IP to maddr parameter of that Contact header as
This is the 200 OK for NOTIFY that passes through my sip proxy and received
SIP/2.0 200 OK
From: <sip:user1 at domain.com>;tag=eu0RxmMX51szGFc-WHymQXvDIWInm3td
To: <sip:chatroom at domain.com>;tag=mNCCjL9ioOCeLch.7Pk8DrgOJWDR1WXw
CSeq: 29089 NOTIFY
Via: SIP/2.0/UDP 192.168.89.82:5060
Contact: <sip:hdnfgkpo at 192.168.89.76:5060;maddr=192.168.58.115>
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE,
server: sipsimple 0.31.0
Sylk seems to be not using the maddr ip in the Contact header of 200OK,
Then this results in, further NOTIFY messages are sent by Sylk to clients
directly, not to my sip proxy.
I guess, a fix needs to be applied, what should I do?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SIPBeyondVoIP