[Serusers] msg's not reaching all the way
Daniel-Constantin MIERLA
mierla at fokus.fraunhofer.de
Fri Apr 25 11:51:17 CEST 2003
Hello,
I have checked the message flow and everything seems to be OK. The only
issue that may cause the bad request is the loose routing and MSN. Jiri
sent some time ago something about M$ Messenger and loose routing -- it
expects to be "lr=true;" or something similarly and I know that this is
fixed in cvs, you have to set the "rr" parameter "enable_full_lr" to "1"
(check the last version of the rr module to be sure about). Please try
again and send back what the results are.
When receiving an error reply (status code greater than 299) from sip
side for a sent message, the jabber gateway automatically closes the
connection to jabber server and sends the INFO message.
Best regards,
Daniel
On 4/23/2003 4:40 PM, magnus melin wrote:
>
>
> hey all!
>
> We´re struggeling with a problem since some time now.
>
> We hade set up an SER - jabber environment, the applications are
> running on differnt servers.
>
>
> SIP-client -------(sip (udp) ) --------> SER-server ----------->
> Jabber-server ------(xml (tcp) ) -------> Jabber-client
> <------------------------------
> <---------- <---- <-------
>
>
>
> Now to the problem.
> There is no problem with registration on either sides, and one can
> send a msg from the SIP- client to jabber-client,
> but when responding from jabber to SIP, the SER sends two MESSAGE to
> the sip-client and get two
> 400 BAD REQUEST (frame 11 & 12 ) back from the client, and then the
> jabber-client goes "away" (frame 19) (losses the tcp-handle ?)
>
> In short: a message is sent from the sipclient to the jabberclient,
> the response from the jabberclient wont display on the sip-client.
> Though it looks like in etherreal that the msg reaches all the way to
> the sip-client.
>
> We have both loose_route() and record_route() (see ser.cfg_jabber
> attached).
>
> Thank's
>
> Best Reg
> Anna & Magnus
>
>
>
>
>
> Frame 7 (520 on wire, 520 captured)
> Frame Number: 7
> Linux cooked capture
> Packet type: Unicast to us (0)
> Source: <MISSING>
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> dhcp164-devel (172.18.3.164)
> Version: 4
> Total Length: 504
> Time to live: 64
> Protocol: UDP (0x11)
> Source: dhcp164-devel (172.18.3.164)
> Destination: dhcp164-devel (172.18.3.164)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
> Source port: 5060 (5060)
> Destination port: 5060 (5060)
> Length: 484
> Checksum: 0xb971 (correct)
> Session Initiation Protocol
> Request line: MESSAGE sip:x at e-horizon.se SIP/2.0
> Message Header
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> To: sip:x at e-horizon.se
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> CSeq: 10 MESSAGE
> Call-ID: 38231eab-9474 at 172.18.3.164
> Content-Length: 20
> User-Agent: Sip EXpress router(0.8.11pre13 (i386/linux))
> Content-Type: text/plain
> Contact: <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>
> Session Description Protocol
> Invalid line: bbbbbbbbbbbbbbbbbbbb
>
>
>
> Frame 8 (674 on wire, 674 captured)
> Linux cooked capture
> Packet type: Sent by us (4)
> Link-layer address type: 1
> Link-layer address length: 6
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> shot.e-horizon.se (172.18.1.66)
> Time to live: 64
> Protocol: UDP (0x11)
> Header checksum: 0xdb50 (correct)
> Source: dhcp164-devel (172.18.3.164)
> Destination: shot.e-horizon.se (172.18.1.66)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 7203 (7203)
> Source port: 5060 (5060)
> Destination port: 7203 (7203)
> Length: 638
> Checksum: 0x6016 (correct)
> Session Initiation Protocol
> Request line: MESSAGE sip:172.18.1.66:7203 SIP/2.0
> Message Header
> Record-Route:
> <sip:x at 172.18.3.164:5060;ftag=949cc72a86e24d5dcb2bf51338531b31-4809;lr>
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bK8984.7c66ebe.0
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> To: sip:x at e-horizon.se
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> CSeq: 10 MESSAGE
> Call-ID: 38231eab-9474 at 172.18.3.164
> Content-Length: 20
> User-Agent: Sip EXpress router(0.8.11pre13 (i386/linux))
> Content-Type: text/plain
> Contact: <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>
> Session Description Protocol
> Invalid line: bbbbbbbbbbbbbbbbbbbb
>
>
> Frame 9 (520 on wire, 520 captured)
> Linux cooked capture
> Source: <MISSING>
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> dhcp164-devel (172.18.3.164)
> Protocol: UDP (0x11)
> Header checksum: 0xd988 (correct)
> Source: dhcp164-devel (172.18.3.164)
> Destination: dhcp164-devel (172.18.3.164)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
> Source port: 5060 (5060)
> Destination port: 5060 (5060)
> Length: 484
> Session Initiation Protocol
> Request line: MESSAGE sip:x at e-horizon.se SIP/2.0
> Message Header
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> To: sip:x at e-horizon.se
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> CSeq: 10 MESSAGE
> Call-ID: 38231eab-9474 at 172.18.3.164
> Content-Length: 20
> User-Agent: Sip EXpress router(0.8.11pre13 (i386/linux))
> Content-Type: text/plain
> Contact: <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>
> Session Description Protocol
> Invalid line: bbbbbbbbbbbbbbbbbbbb
>
>
>
> Frame 10 (674 on wire, 674 captured)
> Arrival Time: Apr 23, 2003 15:28:20.284421000
> Linux cooked capture
> Packet type: Sent by us (4)
> Link-layer address type: 1
> Link-layer address length: 6
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> shot.e-horizon.se (172.18.1.66)
> Version: 4
> Header length: 20 bytes
> Protocol: UDP (0x11)
> Header checksum: 0xdb50 (correct)
> Source: dhcp164-devel (172.18.3.164)
> Destination: shot.e-horizon.se (172.18.1.66)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 7203 (7203)
> Source port: 5060 (5060)
> Destination port: 7203 (7203)
> Session Initiation Protocol
> Request line: MESSAGE sip:172.18.1.66:7203 SIP/2.0
> Message Header
> Record-Route:
> <sip:x at 172.18.3.164:5060;ftag=949cc72a86e24d5dcb2bf51338531b31-4809;lr>
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bK8984.7c66ebe.0
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> To: sip:x at e-horizon.se
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> CSeq: 10 MESSAGE
> Call-ID: 38231eab-9474 at 172.18.3.164
> Content-Length: 20
> User-Agent: Sip EXpress router(0.8.11pre13 (i386/linux))
> Content-Type: text/plain
> Contact: <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>
> Session Description Protocol
> Invalid line: bbbbbbbbbbbbbbbbbbbb
>
>
>
> Frame 11 (474 on wire, 474 captured)
> Arrival Time: Apr 23, 2003 15:28:20.285190000
> Linux cooked capture
> Packet type: Unicast to us (0)
> Link-layer address type: 1
> Link-layer address length: 6
> Source: 00:05:5d:03:03:1e (D-Link_03:03:1e)
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: shot.e-horizon.se (172.18.1.66), Dst
> Addr: dhcp164-devel (172.18.3.164)
> Time to live: 127
> Protocol: UDP (0x11)
> Header checksum: 0x765a (correct)
> Source: shot.e-horizon.se (172.18.1.66)
> Destination: dhcp164-devel (172.18.3.164)
> User Datagram Protocol, Src Port: 3173 (3173), Dst Port: 5060 (5060)
> Source port: 3173 (3173)
> Destination port: 5060 (5060)
> Length: 438
> Checksum: 0x8c6c (correct)
> Session Initiation Protocol
> Status line: SIP/2.0 400 Bad Request
> Message Header
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bK8984.7c66ebe.0
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> To: sip:x at e-horizon.se;tag=199332f8-e402-4795-833a-c90969c979b0
> Call-ID: 38231eab-9474 at 172.18.3.164
> CSeq: 10 MESSAGE
> User-Agent: Windows RTC/1.0
> Content-Length: 0
>
>
>
>
> Frame 12 (409 on wire, 409 captured)
> Arrival Time: Apr 23, 2003 15:28:20.288277000
> Linux cooked capture
> Packet type: Unicast to us (0)
> Link-layer address type: 772
> Link-layer address length: 0
> Source: <MISSING>
> Protocol: IP (0x0800)
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> dhcp164-devel (172.18.3.164)
> Time to live: 64
> Protocol: UDP (0x11)
> Header checksum: 0xd9f7 (correct)
> Source: dhcp164-devel (172.18.3.164)
> Destination: dhcp164-devel (172.18.3.164)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
> Source port: 5060 (5060)
> Destination port: 5060 (5060)
> Length: 373
> Checksum: 0x4b0e (correct)
> Session Initiation Protocol
> Status line: SIP/2.0 400 Bad Request
> Message Header
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKa858.b1ed4bd6.0
> From:
> <sip:b*storstark.e-horizon.se at jstorstark.e-horizon.se>;tag=949cc72a86e24d5dcb2bf51338531b31-4809
> To: sip:x at e-horizon.se;tag=199332f8-e402-4795-833a-c90969c979b0
> Call-ID: 38231eab-9474 at 172.18.3.164
> CSeq: 10 MESSAGE
> User-Agent: Windows RTC/1.0
> Content-Length: 0
> .
> .
> .
> .
> Frame 19 (530 on wire, 530 captured)
> Frame Number: 19
> Internet Protocol, Src Addr: dhcp164-devel (172.18.3.164), Dst Addr:
> dhcp164-devel (172.18.3.164)
> Version: 4
> Header length: 20 bytes
> Time to live: 64
> Protocol: UDP (0x11)
> Source: dhcp164-devel (172.18.3.164)
> Destination: dhcp164-devel (172.18.3.164)
> User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
> Source port: 5060 (5060)
> Destination port: 5060 (5060)
> Session Initiation Protocol
> Request line: MESSAGE sip:x at e-horizon.se SIP/2.0
> Message Header
> Via: SIP/2.0/UDP 172.18.3.164:5060;branch=z9hG4bKb649.52575b6.0
> To: sip:x at e-horizon.se
> From:
> <sip:sip_to_jabber_gateway>;tag=949cc72a86e24d5dcb2bf51338531b31-dc30
> CSeq: 10 MESSAGE
> Call-ID: 38231eac-9474 at 172.18.3.164
> Content-Length: 85
> User-Agent: Sip EXpress router(0.8.11pre13 (i386/linux))
> Content-Type: text/plain
> Contact: <sip:sip_to_jabber_gateway>
> Session Description Protocol
> Invalid line: INFO: Your are now offline in Jabber network. Thank you
> for using SIP-Jabber gateway.
More information about the sr-users
mailing list