[SIP Beyond VoIP] Another case where Sylk would reject Notifications

Hadzhiev, Tihomir tihomir.hadzhiev at acision.com
Fri Nov 16 15:09:32 CET 2012

Well, the IMS client is acknowledging the NOTIFY, als in the IMS client I can see the XMPP user as Active Subscribe, another screenshot from the IMS client this time.

[cid:image001.png at 01CDC40C.61FA2ED0]

Again the problem is that the XMPP Guy doesn't see online the IMS guy

[cid:image002.png at 01CDC40C.61FA2ED0]

Sam happens even if I use Psi. The same behavior is there when I'm using EjabberD and Tigase XMPP servers.

Any suggestions where I can look are more than welcome :(



-----Original Message-----
From: Saúl Ibarra Corretgé [mailto:saul at ag-projects.com]
Sent: 16 November 2012 15:01
To: Hadzhiev, Tihomir
Cc: Adrian Georgescu; sipbeyondvoip at lists.ag-projects.com
Subject: Re: [SIP Beyond VoIP] Another case where Sylk would reject Notifications

On Nov 16, 2012, at 2:54 PM, Hadzhiev, Tihomir wrote:

> Well,


> So far I see the NOTIFY sent reaching the SYLK as I said:


> 9/NOTIFY sip:wbfhcopd at SIP/2.0

> Via: SIP/2.0/UDP;branch=z9hG4bKa4f2.97be7075.0

> Via: SIP/2.0/UDP;branch=z9hG4bKa4f2.731ff2d4.0

> To: sip:admin at testing.com;tag=mHf.-BnNdhzEn2zr6AsK0BoHmC5Eujdk

> From:

> sip:alice at open-ims.test;tag=48b5b8952e8d0bca6256941910840e90-4492

> CSeq: 3 NOTIFY

> Call-ID: XgdwiaQJ7moYV.obv2s97NMJIWy-5Wtw

> Content-Length: 1210

> User-Agent: kamailio (3.3.2 (x86_64/linux))

> Max-Forwards: 16

> Event: presence

> Contact: <sip:;transport=udp>

> Subscription-State: active;expires=3563

> Content-Type: application/pidf+xml


> <?xml version="1.0" encoding="utf-8"?> <presence

> xmlns:cp="urn:ietf:params:xml:ns:pidf:cipid" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:p="urn:ietf:params:xml:ns:pidf-diff" xmlns:op="urn:oma:xml:prs:pidf:oma-pres" xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:alice at open-ims.test">

>   <pdm:person id="JXEEVCMM">

>     <op:overriding-willingness>

>       <op:basic>open</op:basic>

>     </op:overriding-willingness>

>     <rpid:activities>

>       <rpid:unknown/>

>     </rpid:activities>

>     <rpid:mood>

>       <rpid:neutral/>

>     </rpid:mood>

>     <cp:homepage>http://dir.bg</cp:homepage<http://dir.bg%3c/cp:homepage>>

>     <pdm:note>TEST TEXT</pdm:note>

>   </pdm:person>

>   <pdm:device id="d0001">

>     <status>

>       <basic>open</basic>

>     </status>

>     <caps:devcaps>

>       <caps:mobility>

>         <cap


> And notification responded with OK.


> Then finally Sylk replies with HTTP ACCEPTED 202 to the SUBSCRIBE

> request


> Sylk then generates NOTIFY towards the SIP used with event Presence

> and Subscription state - Pending


> Sylk generates the following XMPP presence state towards XMPP server


> <presence to='admin at testing.com' from='alice at open-ims.test'

> type='subscribe'/><presence

> to='admin at testing.com'from='alice at open-ims.test' type='probe'/>



> NOTIFY responded to Sylk on the pending status


> XMPP server send to Sylk OK - Subscribed


> Sylk generateds a NOTIFY towards the IMS user with event Presence and

> Subscription state - Active


> XMPP server send to sylk the following:   <presence from="admin at testing.com/Gajim<mailto:admin at testing.com/Gajim>" to="alice at open-ims.test<mailto:alice at open-ims.test>" id="173"><priority>50</priority><x xmlns="vcard-temp:x:update"><photo/></x><c node="http://gajim.org" xmlns="http://jabber.org/protocol/caps" hash="sha-1" ver="47EPEmSc9oqPGwcrbNtpKcYyJcE="/></presence>


> The NOTIFY gets replied with OK


> The Sylk generates another NOTIFY towards IMS user as follows:


> a|NOTIFY sip:alice at;transport=udp SIP/2.0

> Via: SIP/2.0/UDP


> Qk

> Max-Forwards: 70

> From: <sip:admin at testing.com>;tag=d410yOgImEyvLf-bii0VU4vFx-vITCVx

> To: <sip:alice at open-ims.test>;tag=12673

> Contact: <sip:admin at>

> Call-ID: M-b4fced012e3884d755287520b438e711

> CSeq: 7571 NOTIFY

> Route: <sip:mo at;lr>

> Route: <sip:mo at;lr>

> Event: presence

> Subscription-State: active;expires=599999

> Allow-Events: conference, refer, presence

> User-Agent: SylkServer-2.2.1

> Content-Type: application/pidf+xml

> Content-Length:   820


> <?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="admin%40testing.com"><tuple

> id="ID-47616a696d"><status><basic>open</basic><agp-pidf:extended>avail

> able</agp-pidf:extended></status><dm:deviceID>47616a696d</dm:deviceID>

> <agp-pidf:device-info

> id="47616a696d"><agp-pidf:description>Gajim</agp-pidf:description></ag

> p-pidf:device-info><caps:servcaps><caps:message>true</caps:message><ca

> ps:text>true</caps:text></caps:servcaps><contact>sip%3Aadmin%40testing

> .com%3Bxmpp%3Bgr%3D47616a696d</contact></tuple><dm:person

> id="ID-0dc8f8d23b595e70248c34fd05bf8f35"><rpid:activities/></dm:person

> ></presence



> Do you still need the sip, xmpp, notification logs ?


> Could it be a problem of the VCards being generated ? I'm really smashed here... Everything looks like working normally , e.g. at least the flows are looking fine, triggers as well. But can't make it working.


> When I look into the presence server, I see that these 2 users are Actively watching each others ( picture attached ):


I'm confused. If SylkServer is sending the NOTIFY out then the problem must be in the receiving client. Maybe it doesn't like our NOTIFY?


Saúl Ibarra Corretgé

AG Projects

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/2276475d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12773 bytes
Desc: image001.png
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20121116/2276475d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 16482 bytes
Desc: image002.png
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20121116/2276475d/attachment-0003.png>

More information about the SIPBeyondVoIP mailing list