[SIP Beyond VoIP] Another case where Sylk would reject Notifications
Hadzhiev, Tihomir
tihomir.hadzhiev at acision.com
Fri Nov 16 12:25:25 CET 2012
Well,
I see in a dump that Sylk generated the presence subscribption and probe towards the XMPP server ( Ejabberd ) and this is being responded as SUBSCRIBED by EjabberD
Then the following Notify is sent towards IMS from Sylk ( with Tuple populated )
Session Initiation Protocol
Request-Line: NOTIFY sip:alice at 10.226.20.14:55305;transport=udp SIP/2.0
Method: NOTIFY
Request-URI: sip:alice at 10.226.20.14:55305;transport=udp
Request-URI User Part: alice
Request-URI Host Part: 10.226.20.14
Request-URI Host Port: 55305
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 10.226.20.56:6060;rport;branch=z9hG4bKPjRey1TfZpnkw0bWjo17eyzOwe4yIw-0-f
Transport: UDP
Sent-by Address: 10.226.20.56
Sent-by port: 6060
RPort: rport
Branch: z9hG4bKPjRey1TfZpnkw0bWjo17eyzOwe4yIw-0-f
Max-Forwards: 70
From: <sip:tihoparvi at testing.com>;tag=Pxq4QZ-BeM7HHoMWn1HCb7DniVmSnspT
SIP from address: sip:tihoparvi at testing.com
SIP from address User Part: tihoparvi
SIP from address Host Part: testing.com
SIP tag: Pxq4QZ-BeM7HHoMWn1HCb7DniVmSnspT
To: <sip:alice at open-ims.test>;tag=24372
SIP to address: sip:alice at open-ims.test
SIP to address User Part: alice
SIP to address Host Part: open-ims.test
SIP tag: 24372
Contact: <sip:tihoparvi at 10.226.20.56:6060>
Contact-URI: sip:tihoparvi at 10.226.20.56:6060
Contactt-URI User Part: tihoparvi
Contact-URI Host Part: 10.226.20.56
Contact-URI Host Port: 6060
Call-ID: M-874137a0b1349286241207066c1c4e72
CSeq: 15028 NOTIFY
Sequence Number: 15028
Method: NOTIFY
Route: <sip:mo at 10.226.20.240:6060;lr>
Route: <sip:mo at 10.226.20.240:4060;lr>
Event: presence
Subscription-State: active;expires=599996
Allow-Events: conference, refer, presence
User-Agent: SylkServer-2.2.1
Content-Type: application/pidf+xml
Content-Length: 873
Message Body
eXtensible Markup Language
<?xml
version='1.0'
encoding='UTF-8'
?>
<presence
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:agp-pidf="urn:ag-projects:xml:ns:pidf"
xmlns:caps="urn:ietf:params:xml:ns:pidf:caps"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
xmlns="urn:ietf:params:xml:ns:pidf"
entity="tihoparvi%40testing.com">
<tuple
id="ID-435a2d52384c474b4547">
<status>
<basic>
open
</basic>
<agp-pidf:extended>
available
</agp-pidf:extended>
</status>
<dm:deviceID>
435a2d52384c474b4547
</dm:deviceID>
<agp-pidf:device-info
id="435a2d52384c474b4547">
<agp-pidf:description>
CZ-R8LGKEG
</agp-pidf:description>
</agp-pidf:device-info>
<caps:servcaps>
<caps:message>
true
</caps:message>
<caps:text>
true
</caps:text>
</caps:servcaps>
<contact>
sip%3Atihoparvi%40testing.com%3Bxmpp%3Bgr%3D435a2d52384c474b4547
</contact>
</tuple>
<dm:person
id="ID-ed8975ecb63f91ca1146ca625b6fca2d">
<rpid:activities/>
</dm:person>
</presence>
The above pdu is responded with OK
What I don't like at some point is that a Notify from the presence server for the SIP user to the XMPP user with the PDIF is being rejected by the SIP proxy and does not reach Sylk, the error is :
Warning: 392 10.226.20.240:6060 "Noisy feedback tells: pid=8570 req_src_ip=10.226.20.56 req_src_port=5080 in_uri=sip:zvkgjyfh at 10.226.20.56:6060 out_uri=sip:zvkgjyfh at 10.226.20.56:6060 via_cnt==1" but this might not have any relation :(
Is a fact that the presence request reaches the XMPP server correctly, and it is acknowledged. But still I cannot see the IMS user online.
Suggestions ?
Thanks,
Tiho
From: Adrian Georgescu [mailto:ag at ag-projects.com]
Sent: 16 November 2012 11:44
To: Hadzhiev, Tihomir
Cc: sipbeyondvoip at lists.ag-projects.com
Subject: Re: [SIP Beyond VoIP] Another case where Sylk would reject Notifications
Sure, if the PIDF payload in the PIDF conveys this information. Does it?
Adrian
On Nov 16, 2012, at 11:38 AM, Hadzhiev, Tihomir wrote:
Hi all,
I have finally applied a workaround on the Record-Route field, so now it is not populated with FQDNs, instead there are IP addresses and ports.
e.g. Sylk does not crash anymore and I have the following in Sylk's ( --no-fork ) log:
[xmppgateway] Presence session established sip:alice at open-ims.test --> xmpp:tihoparvi at testing.com
[xmppgateway] Presence session established xmpp:tihoparvi at testing.com --> sip:alice at open-ims.test
E.g. it looks like the presence is established correctly.
But now a question.
Once the above presence is established correctly, am I supposed to see the green light ( e.g. user online ) at the XMPP Client for the guy at the SIP end ?
Thanks,
Tiho
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20121116/8981cce6/attachment-0001.html>
More information about the SIPBeyondVoIP
mailing list