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

Adrian Georgescu ag at ag-projects.com
Fri Nov 16 14:31:22 CET 2012


And what happens when it reaches SylkServer?

Please enable sip, xmpp and notifications logs and paste them here.

Regards,
Adrian


On Nov 16, 2012, at 1:57 PM, Hadzhiev, Tihomir wrote:

> I will trace that, meanwhile here is the NOTIFY that reaches SYLK ( including the PDIF ):
> 
> 
> 
> Session Initiation Protocol
>    Request-Line: NOTIFY sip:yndugtca at 10.226.20.56:6060 SIP/2.0
>        Method: NOTIFY
>        Request-URI: sip:yndugtca at 10.226.20.56:6060
>            Request-URI User Part: yndugtca
>            Request-URI Host Part: 10.226.20.56
>            Request-URI Host Port: 6060
>        [Resent Packet: False]
>    Message Header
>        Via: SIP/2.0/UDP 10.226.20.240:6060;branch=z9hG4bKc8f1.91e76551.0
>            Transport: UDP
>            Sent-by Address: 10.226.20.240
>            Sent-by port: 6060
>            Branch: z9hG4bKc8f1.91e76551.0
>        Via: SIP/2.0/UDP 10.226.20.56:5080;branch=z9hG4bKc8f1.788613e5.0
>            Transport: UDP
>            Sent-by Address: 10.226.20.56
>            Sent-by port: 5080
>            Branch: z9hG4bKc8f1.788613e5.0
>        To: sip:admin at testing.com;tag=srEHBlStXmD32JNkPzrTpUnSNdOyji7e
>            SIP to address: sip:admin at testing.com
>                SIP to address User Part: admin
>                SIP to address Host Part: testing.com
>            SIP tag: srEHBlStXmD32JNkPzrTpUnSNdOyji7e
>        From: sip:alice at open-ims.test;tag=48b5b8952e8d0bca6256941910840e90-4cf1
>            SIP from address: sip:alice at open-ims.test
>                SIP from address User Part: alice
>                SIP from address Host Part: open-ims.test
>            SIP tag: 48b5b8952e8d0bca6256941910840e90-4cf1
>        CSeq: 6 NOTIFY
>            Sequence Number: 6
>            Method: NOTIFY
>        Call-ID: hGi71RUziL3L.EMyMfZvpnRT43CwjkhJ
>        Content-Length: 1210
>        User-Agent: kamailio (3.3.2 (x86_64/linux))
>        Max-Forwards: 16
>        Event: presence
>        Contact: <sip:10.226.20.56:5080;transport=udp>
>            Contact-URI: sip:10.226.20.56:5080;transport=udp
>                Contact-URI Host Part: 10.226.20.56
>                Contact-URI Host Port: 5080
>            Contact parameter: transport=udp>
>        Subscription-State: active;expires=2718
>        Content-Type: application/pidf+xml
>    Message Body
>        eXtensible Markup Language
>            <?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>
>                    <pdm:note>
>                        TEST TEXT
>                        </pdm:note>
>                    </pdm:person>
>                <pdm:device
>                    id="d0001">
>                    <status>
>                        <basic>
>                            open
>                            </basic>
>                        </status>
>                    <caps:devcaps>
>                        <caps:mobility>
>                            <caps:supported>
>                                <caps:fixed/>
>                                </caps:supported>
>                            </caps:mobility>
>                        </caps:devcaps>
>                    <op:network-availability>
>                        <op:network
>                            id="IMS">
>                            <op:active/>
>                            </op:network>
>                        </op:network-availability>
>                    <pdm:deviceID>
>                        urn:uuid:3ca50bcb-7a67-44f1-afd0-994a55f930f4
>                        </pdm:deviceID>
>                    </pdm:device>
>                </presence>
> 
> -----Original Message-----
> From: Saúl Ibarra Corretgé [mailto:saul at ag-projects.com]
> Sent: 16 November 2012 13:45
> 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 1:37 PM, Hadzhiev, Tihomir wrote:
> 
>> Well I see that the NOTIFY reaches Sylk, and SYLK says OK on the notify, the notify is sent towards the generated address, for example:
>> 
>> Contact URI: yndugtca at 10.226.20.56:6060      which is Sylk.
>> 
> 
> Then I guess there is something about the NOTIFY that Sylk isn't liking that much. You can add some debug prints in presence.py to track it down.
> 
>> Also what I see is that Sylk replies with HTTP OK 202 on the SUBSCRIBES -> Is this correct ?
>> 
> 
> Yes.
> 
>> Cheers,
>> Tiho
>> 
>> 
>> -----Original Message-----
>> From: Saúl Ibarra Corretgé [mailto:saul at ag-projects.com]
>> Sent: 16 November 2012 12:35
>> 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 12:25 PM, Hadzhiev, Tihomir wrote:
>> 
>>> 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 L
>>> 
>>> 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.
>>> 
>> 
>> Does the NOTIFY reach SylkServer? If it doesn't then there not nothing SylkServer can do about it.
>> 
>> --
>> 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.
>> 
>> 
> 
> --
> 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.
> 
> 



More information about the SIPBeyondVoIP mailing list