[SR-Users] Routing Problems (Sorry, Text file is now included)

Andreas Rehbein rehbein at e-technik.org
Thu Feb 4 15:21:59 CET 2010 

Hello,

 

we use Kamailio 3.0 on a Red Hat EL5.4 system with openssl 0.9.8e (the
current Red Hat OpenSSL version). We want to use Kamailio 3.0 in front of
our Call Server (OpenSER 1.3.2) as a security gateway. So the Call Server
should only deal tcp, while the Security Gateway terminates the TLS Data
which he receives from the User Agents but forwards the SIP-Messages via TCP
to the Call Server.

 

UA ---SIP_over_TLS---> Security Gateway (Kam3.0) ---SIP_over_TCP---> Call
Server (OpenSER1.3.2)

UA<---SIP_over_TLS--- Security Gateway (Kam3.0) <---SIP_over_TCP--- Call
Server (OpenSER1.3.2)

 

Nearly everything works fine in this scenario: User Agents are able to
register and when they are sending INVITES the callee receives it. 

The problem we have right now is: if Kamailio 3.0 receives BYE we get "477
Unfortunatly error on sending to next hop occured". It seems that the
messages are ok...

I attached a text file with the BYE message and the errors.

 

Explanation for the text file: 

* UA1: 192.168.0.126

* UA2: 192.168.0.176

*Security Gateway (Kam3.0): 192.168.0.89

*Call Server (OpenSER1.3.2): 192.168.0.106

 

No.     Time        Source                Destination           Protocol
Info

    101 7.964015    192.168.0.106         192.168.0.89          SIP
Request: BYE sip:+497118113608227 at 192.168.0.89:37260;transport=TLS

 

Frame 101 (1138 bytes on wire, 1138 bytes captured)

Ethernet II, Src: AlliedTe_3e:b8:05 (00:15:77:3e:b8:05), Dst: Dell_a0:e2:3f
(00:1c:23:a0:e2:3f)

Internet Protocol, Src: 192.168.0.106 (192.168.0.106), Dst: 192.168.0.89
(192.168.0.89)

Transmission Control Protocol, Src Port: 50445 (50445), Dst Port: sip
(5060), Seq: 1234, Ack: 1, Len: 1072

Session Initiation Protocol

    Request-Line: BYE sip:+497118113608227 at 192.168.0.89:37260;transport=TLS
SIP/2.0

    Message Header

        Record-Route: <sip:192.168.0.106;transport=tcp;lr=on;ftag=ba3448a0>

        Record-Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on>

        Record-Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on>

        Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19

        Via: SIP/2.0/TCP
192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a

        Via: SIP/2.0/TLS
192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport
=1876

        Max-Forwards: 68

        Route: <sip:192.168.0.89;transport=tcp;r2=on;lr=on>

        Route: <sip:192.168.0.89:5061;transport=tls;r2=on;lr=on>

        Contact:
<sip:+497118113608226 at 192.168.0.89:37260;transport=TLS;rinstance=972e46956fc
87f26>

        To:
"+497118113608227"<sip:+497118113608227 at 192.168.0.106>;tag=15c25277

        From: <sip:+497118113608226 at 192.168.0.106>;tag=ba3448a0

        Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ.

        CSeq: 2 BYE

        User-Agent: Bosch Communicator release 2.5.4.2 GAC4 stamp 54836

        Reason: SIP;description="User Hung Up"

        Content-Length: 0

        P-hint: rr-enforced

 

No.     Time        Source                Destination           Protocol
Info

    103 7.964791    192.168.0.89          192.168.0.106         SIP
Status: 477 Unfortunately error on sending to next hop occurred (477/SL)

 

Frame 103 (887 bytes on wire, 887 bytes captured)

Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05
(00:15:77:3e:b8:05)

Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106
(192.168.0.106)

Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445
(50445), Seq: 1, Ack: 2306, Len: 821

Session Initiation Protocol

    Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop
occurred (477/SL)

    Message Header

        Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19

        Via: SIP/2.0/TCP
192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a

        Via: SIP/2.0/TLS
192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport
=1876

        To:
"+497118113608227"<sip:+497118113608227 at 192.168.0.106>;tag=15c25277

        From: <sip:+497118113608226 at 192.168.0.106>;tag=ba3448a0

        Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ.

        CSeq: 2 BYE

        Server: kamailio (3.0.0 (i386/linux))

        Content-Length: 0

        [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells:
pid=10378 req_src_ip=192.168.0.106 req_src_port=50445
in_uri=sip:+497118113608227 at 192.168.0.89:37260;transport=TLS
out_uri=sip:+497118113608227 at 192.168.0.89:37260;transport

 

No.     Time        Source                Destination           Protocol
Info

    104 7.964845    192.168.0.89          192.168.0.106         SIP
Status: 477 Unfortunately error on sending to next hop occurred (477/TM)

 

Frame 104 (887 bytes on wire, 887 bytes captured)

Ethernet II, Src: Dell_a0:e2:3f (00:1c:23:a0:e2:3f), Dst: AlliedTe_3e:b8:05
(00:15:77:3e:b8:05)

Internet Protocol, Src: 192.168.0.89 (192.168.0.89), Dst: 192.168.0.106
(192.168.0.106)

Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50445
(50445), Seq: 822, Ack: 2306, Len: 821

Session Initiation Protocol

    Status-Line: SIP/2.0 477 Unfortunately error on sending to next hop
occurred (477/TM)

    Message Header

        Via: SIP/2.0/TCP 192.168.0.106;branch=z9hG4bK854f.b305c913.0;i=19

        Via: SIP/2.0/TCP
192.168.0.89;rport=37260;branch=z9hG4bK854f.dac34f77.0;i=a

        Via: SIP/2.0/TLS
192.168.0.126:62399;branch=z9hG4bK-d8754z-51f50d6cfa997da7-1---d8754z-;rport
=1876

        To:
"+497118113608227"<sip:+497118113608227 at 192.168.0.106>;tag=15c25277

        From: <sip:+497118113608226 at 192.168.0.106>;tag=ba3448a0

        Call-ID: ZjdiMWY5NTYxMTMyN2Q5NTkwOWVmZWExOTEwMDhjYzQ.

        CSeq: 2 BYE

        Server: kamailio (3.0.0 (i386/linux))

        Content-Length: 0

        [truncated] Warning: 392 192.168.0.89:5060 "Noisy feedback tells:
pid=10378 req_src_ip=192.168.0.106 req_src_port=50445
in_uri=sip:+497118113608227 at 192.168.0.89:37260;transport=TLS
out_uri=sip:+497118113608227 at 192.168.0.89:37260;transport

 

Do you have any suggestions?

Thank you very much in advance!

 

Regards

Andreas

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20100204/11da8cfd/attachment.htm>

More information about the sr-users mailing list