[jitsi-dev] About Jitsi 4088 windows build, handling the Subscription-State: terminated


#1

HI

I have tested jitsi 4088 windows build with following setup:

ip network is: 192.168.122.0
101(.224) --- proxy (.32) --- 102 (.147)

     101/102: jitsi window buid 4088, configured with xcap as storage/SIMPLE ( SIP)
     proxy is kamailio 3.3
     101 has 102 as contact, 102 has 101 as contact

     now at client 101, remove 102 from its contact lists,
     thus Kamailio sent NOTIFY to 102 as:

(1) if send:
      Subscription-State: terminated;reason=probation,retry-after=300

      According to RFC 3265:

   probation: The subscription has been terminated, but the client
       SHOULD retry at some later time. If a "retry-after" parameter is
       also present, the client SHOULD wait at least the number of
       seconds specified by that parameter before attempting to re-
       subscribe.

        The client should re-subscribes at least "retry-after" seconds.

        According to the test trace, jitis does NOT honor this retry-after, instead it keeps on sending re-subcribes may 5-15 seconds?

(2) if send :
       Subscription-State: terminated;reason=deactivated.

According to RFC 3265:

    deactivated: The subscription has been terminated, but the subscriber
       SHOULD retry immediately with a new subscription. One primary use
       of such a status code is to allow migration of subscriptions
       between nodes. The "retry-after" parameter has no semantics for
       "deactivated".

     The client should send re-subscribe immediately, right?

     but jitsi 102 instead : remove 101 from its pres-rules/resource-lists, and did not send out re-subscribe!

     some part of trace is following: ( if needed I can send out whole trace.)

///// here is part of trace

U 192.168.122.32:5060 -> 192.168.122.147:5060
NOTIFY sip:102@192.168.122.147:5060;transport=udp;registering_acc=192_168_122_32 SIP/2.0.
Via: SIP/2.0/UDP 192.168.122.32;branch=z9hG4bK84bd.f0701d15.0.

From: sip:101@192.168.122.32;tag=a6a1c5f60faecf035a1ae5b6e96e979a-8417.

CSeq: 3 NOTIFY.
Call-ID: f64c8b287bf093000b2b2190cc4e1ef3@0.0.0.0.
Content-Length: 0.
User-Agent: kamailio (3.3.0 (x86_64/linux)).
Max-Forwards: 70.
Event: presence.
Contact: <sip:192.168.122.32:5060;transport=udp>.
Subscription-State: terminated;reason=deactivated.

PUT /xcap-root/pres-rules/users/sip:102@192.168.122.32/presrules HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1134.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 570.
Content-Type: application/auth-policy+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><ruleset xmlns="urn:ietf:params:xml:ns:common-policy"><rule id="presence_allow"><conditions/><actions><sub-handling xmlns="urn:ietf:params:xml:ns:pres-rules">allow</sub-handling></actions><transformations><provide-devices xmlns="urn:ietf:params:xml:ns:pres-rules"><all-devices/></provide-devices><provide-persons xmlns="urn:ietf:params:xml:ns:pres-rules"><all-persons/></provide-persons><provide-services xmlns="urn:ietf:params:xml:ns:pres-rules"><all-services/></provide-services></transformations></rule></ruleset>

PUT /xcap-root/resource-lists/users/sip:102@192.168.122.32/index HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1136.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 157.
Content-Type: application/resource-lists+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"><list name="RootGroup"/></resource-lists>

BTW, some backgroup discussion is at:
    http://lists.sip-router.org/pipermail/sr-users/2012-June/073788.html

thanks

min

···

To: sip:102@192.168.122.32;tag=ba25e5c.


#2

Hey Min,

Thanks for reporting this. We'll be looking at it one of these days!

Emil

···

On 28.06.12 00:29, Min Wang wrote:

HI

I have tested jitsi 4088 windows build with following setup:

ip network is: 192.168.122.0
101(.224) --- proxy (.32) --- 102 (.147)

     101/102: jitsi window buid 4088, configured with xcap as
storage/SIMPLE ( SIP)
     proxy is kamailio 3.3
     101 has 102 as contact, 102 has 101 as contact

     now at client 101, remove 102 from its contact lists,
     thus Kamailio sent NOTIFY to 102 as:

(1) if send:
      Subscription-State: terminated;reason=probation,retry-after=300

      According to RFC 3265:

   probation: The subscription has been terminated, but the client
       SHOULD retry at some later time. If a "retry-after" parameter is
       also present, the client SHOULD wait at least the number of
       seconds specified by that parameter before attempting to re-
       subscribe.

        The client should re-subscribes at least "retry-after" seconds.

        According to the test trace, jitis does NOT honor this
retry-after, instead it keeps on sending re-subcribes may 5-15 seconds?

(2) if send :
       Subscription-State: terminated;reason=deactivated.

According to RFC 3265:

    deactivated: The subscription has been terminated, but the subscriber
       SHOULD retry immediately with a new subscription. One primary use
       of such a status code is to allow migration of subscriptions
       between nodes. The "retry-after" parameter has no semantics for
       "deactivated".

     The client should send re-subscribe immediately, right?

     but jitsi 102 instead : remove 101 from its
pres-rules/resource-lists, and did not send out re-subscribe!

     some part of trace is following: ( if needed I can send out whole
trace.)

///// here is part of trace

U 192.168.122.32:5060 -> 192.168.122.147:5060
NOTIFY
sip:102@192.168.122.147:5060;transport=udp;registering_acc=192_168_122_32 SIP/2.0.
Via: SIP/2.0/UDP 192.168.122.32;branch=z9hG4bK84bd.f0701d15.0.
To: sip:102@192.168.122.32;tag=ba25e5c.
From: sip:101@192.168.122.32;tag=a6a1c5f60faecf035a1ae5b6e96e979a-8417.
CSeq: 3 NOTIFY.
Call-ID: f64c8b287bf093000b2b2190cc4e1ef3@0.0.0.0.
Content-Length: 0.
User-Agent: kamailio (3.3.0 (x86_64/linux)).
Max-Forwards: 70.
Event: presence.
Contact: <sip:192.168.122.32:5060;transport=udp>.
Subscription-State: terminated;reason=deactivated.

PUT /xcap-root/pres-rules/users/sip:102@192.168.122.32/presrules HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1134.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 570.
Content-Type: application/auth-policy+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><ruleset
xmlns="urn:ietf:params:xml:ns:common-policy"><rule
id="presence_allow"><conditions/><actions><sub-handling
xmlns="urn:ietf:params:xml:ns:pres-rules">allow</sub-handling></actions><transformations><provide-devices
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-devices/></provide-devices><provide-persons
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-persons/></provide-persons><provide-services
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-services/></provide-services></transformations></rule></ruleset>

PUT /xcap-root/resource-lists/users/sip:102@192.168.122.32/index HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1136.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 157.
Content-Type: application/resource-lists+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><resource-lists
xmlns="urn:ietf:params:xml:ns:resource-lists"><list
name="RootGroup"/></resource-lists>

BTW, some backgroup discussion is at:
    http://lists.sip-router.org/pipermail/sr-users/2012-June/073788.html

thanks

min

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#3

HI Emil

        thanks for looking at it.

kind regards.

min

···

On 07/10/2012 12:27 PM, Emil Ivov wrote:

Hey Min,

Thanks for reporting this. We'll be looking at it one of these days!

Emil

On 28.06.12 00:29, Min Wang wrote:
   

HI

I have tested jitsi 4088 windows build with following setup:

ip network is: 192.168.122.0
101(.224) --- proxy (.32) --- 102 (.147)

      101/102: jitsi window buid 4088, configured with xcap as
storage/SIMPLE ( SIP)
      proxy is kamailio 3.3
      101 has 102 as contact, 102 has 101 as contact

      now at client 101, remove 102 from its contact lists,
      thus Kamailio sent NOTIFY to 102 as:

(1) if send:
       Subscription-State: terminated;reason=probation,retry-after=300

       According to RFC 3265:

    probation: The subscription has been terminated, but the client
        SHOULD retry at some later time. If a "retry-after" parameter is
        also present, the client SHOULD wait at least the number of
        seconds specified by that parameter before attempting to re-
        subscribe.

         The client should re-subscribes at least "retry-after" seconds.

         According to the test trace, jitis does NOT honor this
retry-after, instead it keeps on sending re-subcribes may 5-15 seconds?

(2) if send :
        Subscription-State: terminated;reason=deactivated.

According to RFC 3265:

     deactivated: The subscription has been terminated, but the subscriber
        SHOULD retry immediately with a new subscription. One primary use
        of such a status code is to allow migration of subscriptions
        between nodes. The "retry-after" parameter has no semantics for
        "deactivated".

      The client should send re-subscribe immediately, right?

      but jitsi 102 instead : remove 101 from its
pres-rules/resource-lists, and did not send out re-subscribe!

      some part of trace is following: ( if needed I can send out whole
trace.)

///// here is part of trace

U 192.168.122.32:5060 -> 192.168.122.147:5060
NOTIFY
sip:102@192.168.122.147:5060;transport=udp;registering_acc=192_168_122_32 SIP/2.0.
Via: SIP/2.0/UDP 192.168.122.32;branch=z9hG4bK84bd.f0701d15.0.
To: sip:102@192.168.122.32;tag=ba25e5c.
From: sip:101@192.168.122.32;tag=a6a1c5f60faecf035a1ae5b6e96e979a-8417.
CSeq: 3 NOTIFY.
Call-ID: f64c8b287bf093000b2b2190cc4e1ef3@0.0.0.0.
Content-Length: 0.
User-Agent: kamailio (3.3.0 (x86_64/linux)).
Max-Forwards: 70.
Event: presence.
Contact:<sip:192.168.122.32:5060;transport=udp>.
Subscription-State: terminated;reason=deactivated.

PUT /xcap-root/pres-rules/users/sip:102@192.168.122.32/presrules HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1134.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 570.
Content-Type: application/auth-policy+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><ruleset
xmlns="urn:ietf:params:xml:ns:common-policy"><rule
id="presence_allow"><conditions/><actions><sub-handling
xmlns="urn:ietf:params:xml:ns:pres-rules">allow</sub-handling></actions><transformations><provide-devices
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-devices/></provide-devices><provide-persons
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-persons/></provide-persons><provide-services
xmlns="urn:ietf:params:xml:ns:pres-rules"><all-services/></provide-services></transformations></rule></ruleset>

PUT /xcap-root/resource-lists/users/sip:102@192.168.122.32/index HTTP/1.0.
P-NGCP-Src-Ip: 192.168.122.147.
P-NGCP-Src-Port: 1136.
Host: 127.0.0.1:5060.
Connection: close.
Content-Length: 157.
Content-Type: application/resource-lists+xml.
Content-Encoding: UTF-8.
User-Agent: Apache-HttpClient/4.1.2 (java 1.5).
.
<?xml version="1.0" encoding="UTF-8" standalone="no"?><resource-lists
xmlns="urn:ietf:params:xml:ns:resource-lists"><list
name="RootGroup"/></resource-lists>

BTW, some backgroup discussion is at:
     http://lists.sip-router.org/pipermail/sr-users/2012-June/073788.html

thanks

min