List Info

Thread: Notification fails - why?
Notification fails - why?
country flaguser name
Germany		 2007-04-25 02:35:23 
Hi!

Could one of you have a look at the following sniffered
communication? The Notification fails and I have absolutely
no idea why. I'm trying to establish a communicaton between
the sip client "x-lite" and an own application. My
own application is running on 192.168.67.23 Can someone
help?

Thanks!

Session Initiation Protocol
    Request-Line: SUBSCRIBE sip:fznty192.168.67.23 SIP/2.0
        Method: SUBSCRIBE
        Resent Packet: False
    Message Header
        Via: SIP/2.0/UDP
192.168.2.38:64516;branch=z9hG4bK-d87543-88002f62dc56217d-1-
-d87543-
        Max-Forwards: 70
        Contact: <sip:franz192.168.2.38:64516>
            Contact Binding: <sip:franz192.168.2.38:64516>
                URI: <sip:franz192.168.2.38:64516>
                    SIP contact address: sip:franz192.168.2.38:64516
        To: <sip:fznty192.168.67.23>
            SIP to address: sip:fznty192.168.67.23
        From: "franz"<sip:franz192.168.67.23>;tag=df09751f
            SIP Display info: "franz"
            SIP from address: sip:franz192.168.67.23
            SIP tag: df09751f
        Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 SUBSCRIBE
        Expires: 300
        Accept: multipart/related, application/rlmi+xml,
application/pidf+xml
        Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
NOTIFY, MESSAGE, SUBSCRIBE, INFO
        User-Agent: X-Lite release 1006e stamp 34025
        Event: presence
        Content-Length: 0


Session Initiation Protocol
    Status-Line: SIP/2.0 200 OK
        Status-Code: 200
        Resent Packet: False
    Message Header
        Via: SIP/2.0/UDP
192.168.2.38:64516;branch=z9hG4bK-d87543-88002f62dc56217d-1-
-d87543-
        To: <sip:fznty192.168.67.23>;tag=29145918
            SIP to address: sip:fznty192.168.67.23
            SIP tag: 29145918
        From: "franz" <sip:franz192.168.67.23>;tag=df09751f
            SIP Display info: "franz" 
            SIP from address: sip:franz192.168.67.23
            SIP tag: df09751f
        Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 SUBSCRIBE
        Expires: 300
        Content-Length: 0


Session Initiation Protocol
    Request-Line: NOTIFY sip:franz192.168.2.38:64516 SIP/2.0
        Method: NOTIFY
        Resent Packet: False
    Message Header
        Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 NOTIFY
        From: <sip:fznty192.168.67.23>;tag=29145918
            SIP from address: sip:fznty192.168.67.23
            SIP tag: 29145918
        To: "franz" <sip:franz192.168.67.23>;tag=df09751f
            SIP Display info: "franz" 
            SIP to address: sip:franz192.168.67.23
            SIP tag: df09751f
        Max-Forwards: 70
        Event:  presence
        Subscription-State: Active;expires=299
        Via: SIP/2.0/UDP
192.168.67.23:5060;branch=z9hG4bK5ec72dd3452b8c09d3b777d04c2
2547f
        Content-Length: 0


Session Initiation Protocol
    Status-Line: SIP/2.0 481 Call/Transaction Does Not
Exist
        Status-Code: 481
        Resent Packet: False
    Message Header
        Via: SIP/2.0/UDP
192.168.67.23:5060;branch=z9hG4bK5ec72dd3452b8c09d3b777d04c2
2547f
        To: "franz"<sip:franz192.168.67.23>;tag=df09751f
            SIP Display info: "franz"
            SIP to address: sip:franz192.168.67.23
            SIP tag: df09751f
        From: <sip:fznty192.168.67.23>;tag=29145918
            SIP from address: sip:fznty192.168.67.23
            SIP tag: 29145918
        Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 NOTIFY
        Accept-Language: en
        Content-Length: 0


____________________________________________________________
___
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192


_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
Re: Notification fails - why?
user name
 2007-04-25 05:40:51 
The 200 OK response to the SUBSCRIBE does not have your
application's
Contact. Therefore, XLite did not create dialog.

On 4/25/07, Franz Fischer <Franz.FD.Fischerweb.de> wrote:
> Hi!
>
> Could one of you have a look at the following sniffered
communication? The Notification fails and I have absolutely
no idea why. I'm trying to establish a communicaton between
the sip client "x-lite" and an own application. My
own application is running on 192.168.67.23 Can someone
help?
>
> Thanks!
>
> Session Initiation Protocol
>     Request-Line: SUBSCRIBE sip:fznty192.168.67.23 SIP/2.0
>         Method: SUBSCRIBE
>         Resent Packet: False
>     Message Header
>         Via: SIP/2.0/UDP
192.168.2.38:64516;branch=z9hG4bK-d87543-88002f62dc56217d-1-
-d87543-
>         Max-Forwards: 70
>         Contact: <sip:franz192.168.2.38:64516>
>             Contact Binding: <sip:franz192.168.2.38:64516>
>                 URI: <sip:franz192.168.2.38:64516>
>                     SIP contact address: sip:franz192.168.2.38:64516
>         To: <sip:fznty192.168.67.23>
>             SIP to address: sip:fznty192.168.67.23
>         From: "franz"<sip:franz192.168.67.23>;tag=df09751f
>             SIP Display info: "franz"
>             SIP from address: sip:franz192.168.67.23
>             SIP tag: df09751f
>         Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
>         CSeq: 1 SUBSCRIBE
>         Expires: 300
>         Accept: multipart/related,
application/rlmi+xml, application/pidf+xml
>         Allow: INVITE, ACK, CANCEL, OPTIONS, BYE,
REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
>         User-Agent: X-Lite release 1006e stamp 34025
>         Event: presence
>         Content-Length: 0
>
>
> Session Initiation Protocol
>     Status-Line: SIP/2.0 200 OK
>         Status-Code: 200
>         Resent Packet: False
>     Message Header
>         Via: SIP/2.0/UDP
192.168.2.38:64516;branch=z9hG4bK-d87543-88002f62dc56217d-1-
-d87543-
>         To: <sip:fznty192.168.67.23>;tag=29145918
>             SIP to address: sip:fznty192.168.67.23
>             SIP tag: 29145918
>         From: "franz" <sip:franz192.168.67.23>;tag=df09751f
>             SIP Display info: "franz"
>             SIP from address: sip:franz192.168.67.23
>             SIP tag: df09751f
>         Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
>         CSeq: 1 SUBSCRIBE
>         Expires: 300
>         Content-Length: 0
>
>
> Session Initiation Protocol
>     Request-Line: NOTIFY sip:franz192.168.2.38:64516 SIP/2.0
>         Method: NOTIFY
>         Resent Packet: False
>     Message Header
>         Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
>         CSeq: 1 NOTIFY
>         From: <sip:fznty192.168.67.23>;tag=29145918
>             SIP from address: sip:fznty192.168.67.23
>             SIP tag: 29145918
>         To: "franz" <sip:franz192.168.67.23>;tag=df09751f
>             SIP Display info: "franz"
>             SIP to address: sip:franz192.168.67.23
>             SIP tag: df09751f
>         Max-Forwards: 70
>         Event:  presence
>         Subscription-State: Active;expires=299
>         Via: SIP/2.0/UDP
192.168.67.23:5060;branch=z9hG4bK5ec72dd3452b8c09d3b777d04c2
2547f
>         Content-Length: 0
>
>
> Session Initiation Protocol
>     Status-Line: SIP/2.0 481 Call/Transaction Does Not
Exist
>         Status-Code: 481
>         Resent Packet: False
>     Message Header
>         Via: SIP/2.0/UDP
192.168.67.23:5060;branch=z9hG4bK5ec72dd3452b8c09d3b777d04c2
2547f
>         To: "franz"<sip:franz192.168.67.23>;tag=df09751f
>             SIP Display info: "franz"
>             SIP to address: sip:franz192.168.67.23
>             SIP tag: df09751f
>         From: <sip:fznty192.168.67.23>;tag=29145918
>             SIP from address: sip:fznty192.168.67.23
>             SIP tag: 29145918
>         Call-ID:
YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
>         CSeq: 1 NOTIFY
>         Accept-Language: en
>         Content-Length: 0
>
>
>
____________________________________________________________
___
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell
und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementorscs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
Re: Notification fails - why?
user name
 2007-04-25 09:50:59 
   From: Franz Fischer <Franz.FD.Fischerweb.de>

   Could one of you have a look at the following sniffered
   communication? The Notification fails and I have
absolutely no idea
   why. I'm trying to establish a communicaton between the
sip client
   "x-lite" and an own application. My own
application is running on
   192.168.67.23 Can someone help?

I see that the NOTIFY has a zero-length body.  I'm no
expert, but
that's probably no a valid body for the "presence"
event package.
Perhaps X-Lite is giving the wrong error response for this
error
condition?

Dale
_______________________________________________
Sip-implementors mailing list
Sip-implementorscs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinf
o/sip-implementors
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )