Problem mit Sip-Protokoll (Notify)

[fischefr]

Hallo!

Ich versuche mich gerade selbst im implementieren von Sip.
Könnte von euch jemand mal einen Blick auf folgende gesniffte Sip-Kommunikation werfen? Für Notify bekomme ich einen Fehler zurück, habe aber keine Ahnung warum. Auf 192.168.67.23 läuft meine Anwendung. Kann mir jemand einen Tipp geben? Client auf 192.168.2.38 ist übrigens Xlite 3.0

Session Initiation Protocol
    Request-Line: SUBSCRIBE sip:[email protected] 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:[email protected]:64516>
            Contact Binding: <sip:[email protected]:64516>
                URI: <sip:[email protected]:64516>
                    SIP contact address: sip:[email protected]:64516
        To: <sip:[email protected]>
            SIP to address: sip:[email protected]
        From: "franz"<sip:[email protected]>;tag=df09751f
            SIP Display info: "franz"
            SIP from address: sip:[email protected]
            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:[email protected]>;tag=29145918
            SIP to address: sip:[email protected]
            SIP tag: 29145918
        From: "franz" <sip:[email protected]>;tag=df09751f
            SIP Display info: "franz" 
            SIP from address: sip:[email protected]
            SIP tag: df09751f
        Call-ID: YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 SUBSCRIBE
        Expires: 300
        Content-Length: 0


Session Initiation Protocol
    Request-Line: NOTIFY sip:[email protected]:64516 SIP/2.0
        Method: NOTIFY
        Resent Packet: False
    Message Header
        Call-ID: YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 NOTIFY
        From: <sip:[email protected]>;tag=29145918
            SIP from address: sip:[email protected]
            SIP tag: 29145918
        To: "franz" <sip:[email protected]>;tag=df09751f
            SIP Display info: "franz" 
            SIP to address: sip:[email protected]
            SIP tag: df09751f
        Max-Forwards: 70
        Event:  presence
        Subscription-State: Active;expires=299
        Via: SIP/2.0/UDP 192.168.67.23:5060;branch=z9hG4bK5ec72dd3452b8c09d3b777d04c22547f
        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=z9hG4bK5ec72dd3452b8c09d3b777d04c22547f
        To: "franz"<sip:[email protected]>;tag=df09751f
            SIP Display info: "franz"
            SIP to address: sip:[email protected]
            SIP tag: df09751f
        From: <sip:[email protected]>;tag=29145918
            SIP from address: sip:[email protected]
            SIP tag: 29145918
        Call-ID: YTk2MzQzNTQwZjRkODZkMzBkNDY1OGE0NTIzNWU5NmY.
        CSeq: 1 NOTIFY
        Accept-Language: en
        Content-Length: 0