[Serusers] Windows messenger 5.0 and instant messages not working with ser?
Jiri Kuthan
jiri at iptel.org
Mon Aug 25 16:54:02 CEST 2003
It seems Microsoft Messenger uses a proprietary model for session opening.
4.7 sends a primer MESSAGE, 5.0 sends an INVITE which 4.7 does not understand.
-jiri
At 04:10 PM 8/25/2003, Timo Santi wrote:
>You are probably right. If have send report to MS, so lets see what they
>will answer. Here is SIP messages so that you can also see what is
>happening.
>
>Here is printed messages from capture. If you wan't to
>have captured files I can send those by e-mail.
>
>**********************************************************
>Instant message from messenger 4.7 to messenger 5.0
>message is not received and 4.7 messenger doesn't show
>any error
>**********************************************************
>**********************************************************
>
>
>
>Frame 2 (619 bytes on wire, 619 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 4.7, Dst Addr: SIP
>SERVER
>User Datagram Protocol, Src Port: 3241 (3241), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Request line: MESSAGE sip:timo.santi at finlux.fi SIP/2.0
> Method: MESSAGE
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:7822
> From: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> To: <sip:timo.santi at finlux.fi>
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 MESSAGE
> Contact: <sip:10.1.1.9:7822>
> User-Agent: Windows RTC/1.0
> Content-Type: text/plain; charset=UTF-
>8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA
>9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9A
>DsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAo
>A
> Content-Length: 5
>Session Description Protocol
> Invalid line: qqqqq
>
>Frame 3 (697 bytes on wire, 697 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: SIP SERVER, Dst Addr:
>MESSENGER 5.0
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Request line: MESSAGE sip:192.168.19.127:7752 SIP/2.0
> Method: MESSAGE
> Message Header
> Max-Forwards: 10
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0
> Via: SIP/2.0/UDP 10.1.1.9:7822
> From: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> To: <sip:timo.santi at finlux.fi>
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 MESSAGE
> Contact: <sip:10.1.1.9:7822>
> User-Agent: Windows RTC/1.0
> Content-Type: text/plain; charset=UTF-
>8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA
>9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9A
>DsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAo
>A
> Content-Length: 5
>Session Description Protocol
> Invalid line: qqqqq
>
>Frame 4 (437 bytes on wire, 437 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr: SIP
>SERVER
>User Datagram Protocol, Src Port: 3015 (3015), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Status line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0
> Via: SIP/2.0/UDP 10.1.1.9:7822
> From: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> To:
><sip:timo.santi at finlux.fi>;tag=93cc5f563a2645f49698e4b3f55
>981c9
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 MESSAGE
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 5 (469 bytes on wire, 469 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr: SIP
>SERVER
>User Datagram Protocol, Src Port: 3015 (3015), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0
> Via: SIP/2.0/UDP 10.1.1.9:7822
> From: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> To:
><sip:timo.santi at finlux.fi>;tag=93cc5f563a2645f49698e4b3f55
>981c9
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 MESSAGE
> Contact: <sip:192.168.19.127:7752>
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 6 (408 bytes on wire, 408 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: SIP SERVER, Dst Addr:
>MESSENGER 4.7
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
>7822 (7822)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:7822
> From: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> To:
><sip:timo.santi at finlux.fi>;tag=93cc5f563a2645f49698e4b3f55
>981c9
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 MESSAGE
> Contact: <sip:192.168.19.127:7752>
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 8 (407 bytes on wire, 407 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr:
>MESSENGER 4.7
>User Datagram Protocol, Src Port: 3017 (3017), Dst Port:
>7822 (7822)
>Session Initiation Protocol
> Request line: BYE sip:10.1.1.9:7822 SIP/2.0
> Method: BYE
> Message Header
> Via: SIP/2.0/UDP 192.168.19.127:7752
> Max-Forwards: 70
> From:
><sip:timo.santi at finlux.fi>;tag=93cc5f563a2645f49698e4b3f55
>981c9
> To: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 BYE
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 11 (412 bytes on wire, 412 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 4.7, Dst Addr:
>MESSENGER 5.0
>User Datagram Protocol, Src Port: 3242 (3242), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP 192.168.19.127:7752
> From:
><sip:timo.santi at finlux.fi>;tag=93cc5f563a2645f49698e4b3f55
>981c9
> To: "trainingcenter"
><sip:trainingcenter at finlux.fi>;tag=36d7fa67-ed2d-44e3-
>b020-80bd4acb3acb
> Call-ID: a24f9bfc-79c7-41aa-8ef4-
>4107c733b73a at 10.1.1.9
> CSeq: 1 BYE
> Contact: <sip:10.1.1.9:7822>
> User-Agent: Windows RTC/1.0
> Content-Length: 0
>
>
>
>
>**********************************************************
>Instant message from messenger 5.0 to messenger 5.0
>message is not received and 5.0 messenger
>shows error "The following message could not be delivered
>to all recipients:"
>**********************************************************
>*************************************
>
>Frame 14 (554 bytes on wire, 554 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst
>Addr: SIP SERVER
>User Datagram Protocol, Src Port: 3254 (3254), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Request line: INVITE sip:timo.santi at finlux.fi SIP/2.0
> Method: INVITE
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> Max-Forwards: 70
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To: <sip:timo.santi at finlux.fi>
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> Contact: <sip:10.1.1.9:9549>
> User-Agent: RTC/1.2
> Content-Type: application/sdp
> Content-Length: 97
>Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 0 0 IN IP4 10.1.1.9
> Owner Username: -
> Session ID: 0
> Session Version: 0
> Owner Network Type: IN
> Owner Address Type: IP4
> Owner Address: 10.1.1.9
> Session Name (s): session
> Connection Information (c): IN IP4 10.1.1.9
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 10.1.1.9
> Time Description, active time (t): 0 0
> Session Start Time: 0
> Session Start Time: 0
> Media Description, name and address (m): x-ms-message
>5060 sip null
> Media Type: x-ms-message
> Media Port: 5060
> Media Proto: sip
> Media Format: null
>
>Frame 16 (578 bytes on wire, 578 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: SIP SERVER, Dst Addr:
>MESSENGER 5.0 SENDER
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
>9549 (9549)
>Session Initiation Protocol
> Status line: SIP/2.0 100 trying -- your call is
>important to us
> Status-Code: 100
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To: <sip:timo.santi at finlux.fi>
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> Server: Sip EXpress router (0.8.10 (i386/linux))
> Content-Length: 0
> Warning: 392 80.74.213.68:5060 "Noisy feedback
>tells: pid=17349 req_src_ip=10.1.1.9
>in_uri=sip:timo.santi at finlux.fi
>out_uri=sip:192.168.19.127:7752 via_cnt==1"
>
>Frame 17 (614 bytes on wire, 614 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: SIP SERVER, Dst Addr:
>MESSENGER 5.0 RECEIVER
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Request line: INVITE sip:192.168.19.127:7752 SIP/2.0
> Method: INVITE
> Message Header
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bK20d5.2468f597.0
> Via: SIP/2.0/UDP 10.1.1.9:9549
> Max-Forwards: 69
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To: <sip:timo.santi at finlux.fi>
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> Contact: <sip:10.1.1.9:9549>
> User-Agent: RTC/1.2
> Content-Type: application/sdp
> Content-Length: 97
>Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 0 0 IN IP4 10.1.1.9
> Owner Username: -
> Session ID: 0
> Session Version: 0
> Owner Network Type: IN
> Owner Address Type: IP4
> Owner Address: 10.1.1.9
> Session Name (s): session
> Connection Information (c): IN IP4 10.1.1.9
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 10.1.1.9
> Time Description, active time (t): 0 0
> Session Start Time: 0
> Session Start Time: 0
> Media Description, name and address (m): x-ms-message
>5060 sip null
> Media Type: x-ms-message
> Media Port: 5060
> Media Proto: sip
> Media Format: null
>
>Frame 18 (454 bytes on wire, 454 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst
>Addr: SIP SERVER
>User Datagram Protocol, Src Port: 3015 (3015), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Status line: SIP/2.0 100 Trying
> Status-Code: 100
> Message Header
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bK20d5.2468f597.0
> Via: SIP/2.0/UDP 10.1.1.9:9549
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 19 (628 bytes on wire, 628 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst
>Addr: SIP SERVER
>User Datagram Protocol, Src Port: 3015 (3015), Dst Port:
>5060 (5060)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP
>80.74.213.68;branch=z9hG4bK20d5.2468f597.0
> Via: SIP/2.0/UDP 10.1.1.9:9549
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> Contact: <sip:192.168.19.127:7752>
> User-Agent: RTC/1.2
> Content-Type: application/sdp
> Content-Length: 109
>Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 0 0 IN IP4
>192.168.19.127
> Owner Username: -
> Session ID: 0
> Session Version: 0
> Owner Network Type: IN
> Owner Address Type: IP4
> Owner Address: 192.168.19.127
> Session Name (s): session
> Connection Information (c): IN IP4 192.168.19.127
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 192.168.19.127
> Time Description, active time (t): 0 0
> Session Start Time: 0
> Session Start Time: 0
> Media Description, name and address (m): x-ms-message
>5060 sip null
> Media Type: x-ms-message
> Media Port: 5060
> Media Proto: sip
> Media Format: null
>
>Frame 20 (567 bytes on wire, 567 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: SIP SERVER, Dst Addr:
>MESSENGER 5.0 SENDER
>User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
>9549 (9549)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 INVITE
> Contact: <sip:192.168.19.127:7752>
> User-Agent: RTC/1.2
> Content-Type: application/sdp
> Content-Length: 109
>Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): - 0 0 IN IP4
>192.168.19.127
> Owner Username: -
> Session ID: 0
> Session Version: 0
> Owner Network Type: IN
> Owner Address Type: IP4
> Owner Address: 192.168.19.127
> Session Name (s): session
> Connection Information (c): IN IP4 192.168.19.127
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 192.168.19.127
> Time Description, active time (t): 0 0
> Session Start Time: 0
> Session Start Time: 0
> Media Description, name and address (m): x-ms-message
>5060 sip null
> Media Type: x-ms-message
> Media Port: 5060
> Media Proto: sip
> Media Format: null
>
>Frame 22 (425 bytes on wire, 425 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst
>Addr: MESSENGER 5.0 SENDER
>User Datagram Protocol, Src Port: 3018 (3018), Dst Port:
>9549 (9549)
>Session Initiation Protocol
> Request line: BYE sip:10.1.1.9:9549 SIP/2.0
> Method: BYE
> Message Header
> Via: SIP/2.0/UDP 192.168.19.127:7752
> Max-Forwards: 70
> From:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> To: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 BYE
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 25 (425 bytes on wire, 425 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst
>Addr: MESSENGER 5.0 RECEIVER
>User Datagram Protocol, Src Port: 3255 (3255), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Request line: ACK sip:192.168.19.127:7752 SIP/2.0
> Method: ACK
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> Max-Forwards: 70
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 ACK
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 28 (694 bytes on wire, 694 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst
>Addr: MESSENGER 5.0 RECEIVER
>User Datagram Protocol, Src Port: 3255 (3255), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Request line: MESSAGE sip:192.168.19.127:7752 SIP/2.0
> Method: MESSAGE
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> Max-Forwards: 70
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 2 MESSAGE
> Contact: <sip:10.1.1.9:9549>
> User-Agent: RTC/1.2
> Content-Type: text/plain; charset=UTF-
>8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA
>9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAJQAyADAAMgA7A
>CAARQBGAD0AOwAgAEMATwA9ADAAOwAgAEMAUwA9ADEAOwAgAFAARgA9ADA
>ADQAKAA0ACgA
> Content-Length: 5
>Session Description Protocol
> Invalid line: ttttt
>
>Frame 31 (392 bytes on wire, 392 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst
>Addr: MESSENGER 5.0 RECEIVER
>User Datagram Protocol, Src Port: 3255 (3255), Dst Port:
>7752 (7752)
>Session Initiation Protocol
> Status line: SIP/2.0 200 OK
> Status-Code: 200
> Message Header
> Via: SIP/2.0/UDP 192.168.19.127:7752
> From:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> To: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 1 BYE
> User-Agent: RTC/1.2
> Content-Length: 0
>
>Frame 34 (423 bytes on wire, 423 bytes captured)
>Linux cooked capture
>Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst
>Addr: MESSENGER 5.0 SENDER
>User Datagram Protocol, Src Port: 3018 (3018), Dst Port:
>9549 (9549)
>Session Initiation Protocol
> Status line: SIP/2.0 481 Call Leg/Transaction Does
>Not Exist
> Status-Code: 481
> Message Header
> Via: SIP/2.0/UDP 10.1.1.9:9549
> From: "trainingcenter at finlux.fi"
><sip:trainingcenter at finlux.fi>;tag=2109e870f95843b485f2537
>b4df42fb2;epid=bb96c233b3
> To:
><sip:timo.santi at finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff
>c5bc1
> Call-ID: b2569878755a467c863981bbc2192b49 at 10.1.1.9
> CSeq: 2 MESSAGE
> User-Agent: RTC/1.2
> Content-Length: 0
>**********************************************************
>
>
>-----Original Message-----
>From: Jiri Kuthan [mailto:jiri at iptel.org]
>Sent: 21. elokuuta 2003 8:22
>To: Timo Santi; serusers at lists.iptel.org
>Subject: Re: [Serusers] Windows messenger 5.0 and instant messages not
>working with ser?
>
>We haven't tested against 5.0. The error possibly lies in Messenger
>itself
>-- 481 is mostly sent when dialog processing between two UAs is broken.
>SER inbetween two UAs does not affect dialog state.
>
>Anyhow, we will look at it. Thanks for reporting.
>
>-jiri
>
>At 10:21 PM 8/20/2003, Timo Santi wrote:
>>Hi all,
>>
>>Have anyone else notice any problems with new windows messenger 5.0
>working with ser? Instant messages are working nicely with windows
>messenger 4.7, but with Windows messenger 5.0 voice and video calls are
>working, but messages cannot be sent. In capture I'm receiving "481 Call
>Leg/Transaction Does Not Exist". In SDP it is also saying: invalid line:
>"message text". I have tried with ser 0.8.10 and 0.8.11pre29.
>>
>>-Timo-
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org
>>http://lists.iptel.org/mailman/listinfo/serusers
>
>--
>Jiri Kuthan http://iptel.org/~jiri/
--
Jiri Kuthan http://iptel.org/~jiri/
More information about the sr-users
mailing list