Kamailio 4.3.4: receive_msg(): no via found in reply

List overview All Threads
Download

newer

older

...

Reinvite, rewrite reply SDP?

Grant Bagdasarian

14 Mar 2016 14 Mar '16

12:23 p.m.

Hello,

We're testing kamailio 4.3.4 with two kamailio's communicating with each other. One of them is a gateway with rtpengine at the carrier side, the other is a basic sip router. When calling a destination and cancelling the INVITE a 487 is received from the carrier and directly ACK'd by the first kamailio and in turn is forwarded to the second. But the 487 response received by the 2nd kamailio doesn't have a Via header which results in kamailio printing the error: receive_msg(): no via found in reply.

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Attachments:

attachment.html (text/html — 6.6 KB)

Show replies by date

Daniel-Constantin Mierla

14 Mar 14 Mar

1:44 p.m.

Hello,

what would be relevant here is seeing the INVITE request sent to 10.14.0.1:5060 -- paste it to the mailing list discussion. That is going to be used to generate 487, and the Via stack from it should be used there.

Cheers, Daniel

On 14/03/16 13:23, Grant Bagdasarian wrote:

...

Hello,

We’re testing kamailio 4.3.4 with two kamailio’s communicating with each other. One of them is a gateway with rtpengine at the carrier side, the other is a basic sip router.

When calling a destination and cancelling the INVITE a 487 is received from the carrier and directly ACK’d by the first kamailio and in turn is forwarded to the second.

But the 487 response received by the 2^nd kamailio doesn’t have a Via header which results in kamailio printing the error: receive_msg(): no via found in reply.

Any ideas why the forwarded 487 doesn’t contain a Via header and how to fix this?

Note: IP’s are changed.

Carrier: 10.0.0.1

Kamailio 1: 10.14.0.1

Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=109ac722.

To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.0.0.1:5060

ACK sip:003112345678@10.0.0.1:5060 SIP/2.0.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

Max-Forwards: 67.

To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=109ac722.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

CSeq: 2 ACK.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=109ac722.

To: sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

2:09 p.m.

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

U 10.14.0.2:5060 -> 10.14.0.1:5060 INVITE sip:0031123456789@10.14.0.1:5060 SIP/2.0. Record-Route: sip:10.14.0.2;lr=on. Record-Route: sip:10.14.0.3;lr=on. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. Max-Forwards: 68. Contact: sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89. To: sip:0031123456789@10.14.0.3:5060. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE. Content-Type: application/sdp. User-Agent: Bria 4 release 4.2.1 stamp 78100. Content-Length: 431.

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. To: sip:0031123456789@10.14.0.3:5060. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Server: kamailio (4.3.4 (x86_64/linux)). Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 INVITE sip:0031123456789@10.0.0.1:5060 SIP/2.0. Record-Route: sip:10.14.0.1;lr=on. Record-Route: sip:10.14.0.2;lr=on. Record-Route: sip:10.14.0.3;lr=on. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. Max-Forwards: 67. Contact: sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89. To: sip:0031123456789@10.14.0.3:5060. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE. Content-Type: application/sdp. User-Agent: Bria 4 release 4.2.1 stamp 78100. Content-Length: 431.

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.2:5060 -> 10.14.0.1:5060 CANCEL sip:0031123456789@10.14.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Max-Forwards: 68. To: sip:0031123456789@10.14.0.3:5060. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 CANCEL sip:0031123456789@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Max-Forwards: 67. To: sip:0031123456789@10.14.0.3:5060. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 200 canceling. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. To: sip:0031123456789@10.14.0.3:5060;tag=a6a1c5f60faecf035a1ae5b6e96e979a-52bb. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Server: kamailio (4.3.4 (x86_64/linux)). Content-Length: 0. .

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Server: sbc_5. Content-Length: 0. .

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:0031123456789@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Max-Forwards: 67. To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 ACK. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

15 Mar 15 Mar

7:46 p.m.

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users sr-users-bounces@lists.sip-router.org on behalf of Grant Bagdasarian gb@cm.nl Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

18 Mar 18 Mar

9:05 a.m.

Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian Sent: Tuesday, March 15, 2016 8:47 PM To: 'miconda@gmail.com' miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users <sr-users-bounces@lists.sip-router.orgmailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

9:25 a.m.

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel

On 18/03/16 10:05, Grant Bagdasarian wrote:

...

Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Grant Bagdasarian *Sent:* Tuesday, March 15, 2016 8:47 PM *To:* 'miconda@gmail.com' miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Any ideas how to solve this?

Regards,

Grant

*From:*sr-users <sr-users-bounces@lists.sip-router.org mailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nl mailto:gb@cm.nl> *Sent:* Monday, March 14, 2016 3:09:47 PM *To:* 'miconda@gmail.com'; Kamailio (SER) - Users Mailing List *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1

Kamailio 1: 10.14.0.1

Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

U 10.14.0.2:5060 -> 10.14.0.1:5060

INVITE sip:0031123456789@10.14.0.1:5060 sip:0031123456789@10.14.0.1:5060 SIP/2.0.

Record-Route: sip:10.14.0.2;lr=on.

Record-Route: sip:10.14.0.3;lr=on.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

Max-Forwards: 68.

Contact: sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89.

To: sip:0031123456789@10.14.0.3:5060.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE.

Content-Type: application/sdp.

User-Agent: Bria 4 release 4.2.1 stamp 78100.

Content-Length: 431.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 100 trying -- your call is important to us.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

To: sip:0031123456789@10.14.0.3:5060.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Server: kamailio (4.3.4 (x86_64/linux)).

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.0.0.1:5060

INVITE sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0.

Record-Route: sip:10.14.0.1;lr=on.

Record-Route: sip:10.14.0.2;lr=on.

Record-Route: sip:10.14.0.3;lr=on.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

Max-Forwards: 67.

Contact: sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89.

To: sip:0031123456789@10.14.0.3:5060.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE.

Content-Type: application/sdp.

User-Agent: Bria 4 release 4.2.1 stamp 78100.

Content-Length: 431.

#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.2:5060 -> 10.14.0.1:5060

CANCEL sip:0031123456789@10.14.0.1:5060 sip:0031123456789@10.14.0.1:5060 SIP/2.0.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Max-Forwards: 68.

To: sip:0031123456789@10.14.0.3:5060.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.0.0.1:5060

CANCEL sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Max-Forwards: 67.

To: sip:0031123456789@10.14.0.3:5060.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 200 canceling.

Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

To: sip:0031123456789@10.14.0.3:5060;tag=a6a1c5f60faecf035a1ae5b6e96e979a-52bb.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Server: kamailio (4.3.4 (x86_64/linux)).

Content-Length: 0.

.

#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 200 OK.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.0.0.1:5060

ACK sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0.

Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Max-Forwards: 67.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

From: "+31612345678"sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 ACK.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a.

To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: sip:10.0.0.1:5060.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.

*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Daniel-Constantin Mierla *Sent:* Monday, March 14, 2016 2:44 PM *To:* Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org> *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

what would be relevant here is seeing the INVITE request sent to 10.14.0.1:5060 -- paste it to the mailing list discussion. That is going to be used to generate 487, and the Via stack from it should be used there.

Cheers, Daniel

On 14/03/16 13:23, Grant Bagdasarian wrote:
Hello,



We’re testing kamailio 4.3.4 with two kamailio’s communicating
with each other. One of them is a gateway with rtpengine at the
carrier side, the other is a basic sip router.

When calling a destination and cancelling the INVITE a 487 is
received from the carrier and directly ACK’d by the first kamailio
and in turn is forwarded to the second.

But the 487 response received by the 2^nd kamailio doesn’t have a
Via header which results in kamailio printing the error:
receive_msg(): no via found in reply.



Any ideas why the forwarded 487 doesn’t contain a Via header and
how to fix this?



Note: IP’s are changed.



Carrier: 10.0.0.1

Kamailio 1: 10.14.0.1

Kamailio 2: 10.14.0.2



U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
<sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

To: <sip:003112345678@10.14.0.3:5060>
<sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.0.0.1:5060

ACK sip:003112345678@10.0.0.1:5060
<sip:003112345678@10.0.0.1:5060> SIP/2.0.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

Max-Forwards: 67.

To: <sip:003112345678@10.14.0.3:5060>
<sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>
<sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

CSeq: 2 ACK.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
<sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

To: <sip:003112345678@10.14.0.3:5060>
<sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.



_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

2:43 p.m.

Hi Daniel,

No problem :)

Our devices are kamailios. Our customers use different equipment for sending traffic and I'm not sure what kind of equipment our carriers are using. So, I can't really tell what device they're using. My test was done using Bria (X-Lite) acting as a "customer".

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 10:25 AM To: Grant Bagdasarian gb@cm.nl; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel On 18/03/16 10:05, Grant Bagdasarian wrote: Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian Sent: Tuesday, March 15, 2016 8:47 PM To: 'miconda@gmail.commailto:miconda@gmail.com' miconda@gmail.com mailto:miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users <sr-users-bounces@lists.sip-router.orgmailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.commailto:miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

3:33 p.m.

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

My guess that the sbc_5 is so poor implemented that it takes the Via from last request, which is CANCEL, but CANCEL is a hop-by-hop request in this case. If my guess is confirmed, the implementation of sbc_5 is really far away from RFC3261, something that I haven't probably seen since 2002/3.

To test, you can try to use forward() for CANCEL instead of t_relay(). But you need to know where to send it -- same address as for INVITE -- you can hardcode some values in config for sake of simplicity to test. A proper workaround can be built using htable module to store where the invite was sent, using call-id as a key.

Cheers, Daniel

On 18/03/16 15:43, Grant Bagdasarian wrote:

...

Hi Daniel,

No problem J

Our devices are kamailios. Our customers use different equipment for sending traffic and I’m not sure what kind of equipment our carriers are using. So, I can’t really tell what device they’re using. My test was done using Bria (X-Lite) acting as a “customer”.

Regards,

Grant

*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Sent:* Friday, March 18, 2016 10:25 AM *To:* Grant Bagdasarian gb@cm.nl; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel

On 18/03/16 10:05, Grant Bagdasarian wrote:

Hello Community,



Could someone point me into the right direction for fixing this
issue with CANCEL replies?



Regards,



Grant



*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Grant Bagdasarian
*Sent:* Tuesday, March 15, 2016 8:47 PM
*To:* 'miconda@gmail.com <mailto:miconda@gmail.com>'
<miconda@gmail.com> <mailto:miconda@gmail.com>; Kamailio (SER) -
Users Mailing List <sr-users@lists.sip-router.org>
<mailto:sr-users@lists.sip-router.org>
*Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via
found in reply



Any ideas how to solve this?

Regards,

Grant

------------------------------------------------------------------------

*From:*sr-users <sr-users-bounces@lists.sip-router.org
<mailto:sr-users-bounces@lists.sip-router.org>> on behalf of Grant
Bagdasarian <gb@cm.nl <mailto:gb@cm.nl>>
*Sent:* Monday, March 14, 2016 3:09:47 PM
*To:* 'miconda@gmail.com <mailto:miconda@gmail.com>'; Kamailio
(SER) - Users Mailing List
*Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via
found in reply



Hello Daniel,



Carrier: 10.0.0.1

Kamailio 1: 10.14.0.1

Kamailio 2: 10.14.0.2



I also removed the SDP from the INVITE and the 183 messages.



This is the trace from the Kamailio which directly communicates
with the Carrier.



U 10.14.0.2:5060 -> 10.14.0.1:5060

INVITE sip:0031123456789@10.14.0.1:5060
<sip:0031123456789@10.14.0.1:5060> SIP/2.0.

Record-Route: <sip:10.14.0.2;lr=on>.

Record-Route: <sip:10.14.0.3;lr=on>.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

Max-Forwards: 68.

Contact:
<sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>.

To: <sip:0031123456789@10.14.0.3:5060>.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO,
MESSAGE.

Content-Type: application/sdp.

User-Agent: Bria 4 release 4.2.1 stamp 78100.

Content-Length: 431.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 100 trying -- your call is important to us.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

To: <sip:0031123456789@10.14.0.3:5060>.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Server: kamailio (4.3.4 (x86_64/linux)).

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.0.0.1:5060

INVITE sip:0031123456789@10.0.0.1:5060
<sip:0031123456789@10.0.0.1:5060> SIP/2.0.

Record-Route: <sip:10.14.0.1;lr=on>.

Record-Route: <sip:10.14.0.2;lr=on>.

Record-Route: <sip:10.14.0.3;lr=on>.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

Max-Forwards: 67.

Contact:
<sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>.

To: <sip:0031123456789@10.14.0.3:5060>.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 INVITE.

Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO,
MESSAGE.

Content-Type: application/sdp.

User-Agent: Bria 4 release 4.2.1 stamp 78100.

Content-Length: 431.



#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

Via: SIP/2.0/UDP
10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To: <sip:0031123456789@10.14.0.3:5060>.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.2:5060 -> 10.14.0.1:5060

CANCEL sip:0031123456789@10.14.0.1:5060
<sip:0031123456789@10.14.0.1:5060> SIP/2.0.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

Max-Forwards: 68.

To: <sip:0031123456789@10.14.0.3:5060>.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.0.0.1:5060

CANCEL sip:0031123456789@10.0.0.1:5060
<sip:0031123456789@10.0.0.1:5060> SIP/2.0.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Max-Forwards: 67.

To: <sip:0031123456789@10.14.0.3:5060>.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 200 canceling.

Via: SIP/2.0/UDP
10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-52bb.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Server: kamailio (4.3.4 (x86_64/linux)).

Content-Length: 0.

.



#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 200 OK.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To: <sip:0031123456789@10.14.0.3:5060>.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 CANCEL.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.0.0.1:5060

ACK sip:0031123456789@10.0.0.1:5060
<sip:0031123456789@10.0.0.1:5060> SIP/2.0.

Via: SIP/2.0/UDP
10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

Max-Forwards: 67.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

CSeq: 2 ACK.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



#

U 10.14.0.1:5060 -> 10.14.0.2:5060

SIP/2.0 487 Request Cancelled.

From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

To:
<sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

Contact: <sip:10.0.0.1:5060>.

CSeq: 2 INVITE.

Server: sbc_5.

Content-Length: 0.

.



*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On
Behalf Of *Daniel-Constantin Mierla
*Sent:* Monday, March 14, 2016 2:44 PM
*To:* Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org>>
*Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via
found in reply



Hello,

what would be relevant here is seeing the INVITE request sent to
10.14.0.1:5060 -- paste it to the mailing list discussion. That is
going to be used to generate 487, and the Via stack from it should
be used there.

Cheers,
Daniel

On 14/03/16 13:23, Grant Bagdasarian wrote:

    Hello,



    We’re testing kamailio 4.3.4 with two kamailio’s communicating
    with each other. One of them is a gateway with rtpengine at
    the carrier side, the other is a basic sip router.

    When calling a destination and cancelling the INVITE a 487 is
    received from the carrier and directly ACK’d by the first
    kamailio and in turn is forwarded to the second.

    But the 487 response received by the 2^nd kamailio doesn’t
    have a Via header which results in kamailio printing the
    error: receive_msg(): no via found in reply.



    Any ideas why the forwarded 487 doesn’t contain a Via header
    and how to fix this?



    Note: IP’s are changed.



    Carrier: 10.0.0.1

    Kamailio 1: 10.14.0.1

    Kamailio 2: 10.14.0.2



    U 10.0.0.1:5060 -> 10.14.0.1:5060

    SIP/2.0 487 Request Cancelled.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

    From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
    <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

    To: <sip:003112345678@10.14.0.3:5060>
    <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

    Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

    Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.0.0.1:5060

    ACK sip:003112345678@10.0.0.1:5060
    <sip:003112345678@10.0.0.1:5060> SIP/2.0.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

    Max-Forwards: 67.

    To: <sip:003112345678@10.14.0.3:5060>
    <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

    From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>
    <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

    Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

    CSeq: 2 ACK.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 487 Request Cancelled.

    From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
    <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

    To: <sip:003112345678@10.14.0.3:5060>
    <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

    Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

    Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.




    _______________________________________________

    SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

    sr-users@lists.sip-router.org
    <mailto:sr-users@lists.sip-router.org>

    http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



-- 

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

21 Mar 21 Mar

9 a.m.

Hello Daniel,

Thank you for figuring this out and explaining it to me! This has helped me a lot!

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 4:33 PM To: Grant Bagdasarian gb@cm.nl; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Cheers, Daniel On 18/03/16 15:43, Grant Bagdasarian wrote: Hi Daniel,

No problem :)

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 10:25 AM To: Grant Bagdasarian gb@cm.nl mailto:gb@cm.nl; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel On 18/03/16 10:05, Grant Bagdasarian wrote: Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users <sr-users-bounces@lists.sip-router.orgmailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.commailto:miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

12:17 p.m.

Hi Daniel,

I've tried with htable implementation, but I can't seem to use a variable as the argument for the forward function. I've tried multiple possibilities:

forward($avp(s:cancel_dst)); forward("$avp(s:cancel_dst)");

forward($var(cancel_dst)); forward("$var(cancel_dst)");

forward($sht(cancel=>$ci)); forward("$sht(cancel=>$ci)");

I keep getting the following error:

CRITICAL: <core> [proxy.c:265]: mk_proxy(): could not resolve hostname: "$avp(s:cancel_dst)" Or when I don't enclose the variable in quotes an error about the parameter requiring a string.

I've also tried using the following steps, but rewritehost doesn't allow variables too :(

rewritehost("$var(cancel_dst)"); $du = "sip:$var(cancel_dst):5060;transport=udp";

Any ideas?

Regards,

Grant

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian Sent: Monday, March 21, 2016 10:01 AM To: 'miconda@gmail.com' miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Thank you for figuring this out and explaining it to me! This has helped me a lot!

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 4:33 PM To: Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl>; Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Cheers, Daniel On 18/03/16 15:43, Grant Bagdasarian wrote: Hi Daniel,

No problem :)

Regards,

Grant

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel On 18/03/16 10:05, Grant Bagdasarian wrote: Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users <sr-users-bounces@lists.sip-router.orgmailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.commailto:miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

6:07 p.m.

Hello,

the forward() doesn't take variables as parameter, you have to set $ru or $du to the address where you want to send and then just use forward().

Also, rewrite*() functions do not work with variables.

In assignments, inside the strings of expressions, the vars are not evaluated, you need to use concatenation (+):

$du = "sip:" + $var(cancel_dst) + ":5060;transport=udp";

Cheers, Daniel

On 21/03/16 13:17, Grant Bagdasarian wrote:

...

Hi Daniel,

I’ve tried with htable implementation, but I can’t seem to use a variable as the argument for the forward function.

I’ve tried multiple possibilities:

forward($avp(s:cancel_dst));

forward(“$avp(s:cancel_dst)”);

forward($var(cancel_dst));

forward(“$var(cancel_dst)”);

forward($sht(cancel=>$ci));

forward(“$sht(cancel=>$ci)”);

I keep getting the following error:

CRITICAL: <core> [proxy.c:265]: mk_proxy(): could not resolve hostname: "$avp(s:cancel_dst)"

Or when I don’t enclose the variable in quotes an error about the parameter requiring a string.

I’ve also tried using the following steps, but rewritehost doesn’t allow variables too L

rewritehost(“$var(cancel_dst)”);

$du = "sip:$var(cancel_dst):5060;transport=udp";

Any ideas?

Regards,

Grant

*From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org] *On Behalf Of *Grant Bagdasarian *Sent:* Monday, March 21, 2016 10:01 AM *To:* 'miconda@gmail.com' miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Thank you for figuring this out and explaining it to me! This has helped me a lot!

Regards,

Grant

*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] *Sent:* Friday, March 18, 2016 4:33 PM *To:* Grant Bagdasarian <gb@cm.nl mailto:gb@cm.nl>; Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org> *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Cheers, Daniel

On 18/03/16 15:43, Grant Bagdasarian wrote:

Hi Daniel,



No problem J



Our devices are kamailios. Our customers use different equipment
for sending traffic and I’m not sure what kind of equipment our
carriers are using. So, I can’t really tell what device they’re
using. My test was done using Bria (X-Lite) acting as a “customer”.



Regards,



Grant



*From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com]
*Sent:* Friday, March 18, 2016 10:25 AM
*To:* Grant Bagdasarian <gb@cm.nl> <mailto:gb@cm.nl>; Kamailio
(SER) - Users Mailing List <sr-users@lists.sip-router.org>
<mailto:sr-users@lists.sip-router.org>
*Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via
found in reply



Hello,

with CeBIT trip this week, I didn't get the change to look too
much at it...

What is the device sending the reply to INVITE?

Cheers,
Daniel

On 18/03/16 10:05, Grant Bagdasarian wrote:

    Hello Community,



    Could someone point me into the right direction for fixing
    this issue with CANCEL replies?



    Regards,



    Grant



    *From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org]
    *On Behalf Of *Grant Bagdasarian
    *Sent:* Tuesday, March 15, 2016 8:47 PM
    *To:* 'miconda@gmail.com <mailto:miconda@gmail.com>'
    <miconda@gmail.com> <mailto:miconda@gmail.com>; Kamailio (SER)
    - Users Mailing List <sr-users@lists.sip-router.org>
    <mailto:sr-users@lists.sip-router.org>
    *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no
    via found in reply



    Any ideas how to solve this?

    Regards,

    Grant

    ------------------------------------------------------------------------

    *From:*sr-users <sr-users-bounces@lists.sip-router.org
    <mailto:sr-users-bounces@lists.sip-router.org>> on behalf of
    Grant Bagdasarian <gb@cm.nl <mailto:gb@cm.nl>>
    *Sent:* Monday, March 14, 2016 3:09:47 PM
    *To:* 'miconda@gmail.com <mailto:miconda@gmail.com>'; Kamailio
    (SER) - Users Mailing List
    *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no
    via found in reply



    Hello Daniel,



    Carrier: 10.0.0.1

    Kamailio 1: 10.14.0.1

    Kamailio 2: 10.14.0.2



    I also removed the SDP from the INVITE and the 183 messages.



    This is the trace from the Kamailio which directly
    communicates with the Carrier.



    U 10.14.0.2:5060 -> 10.14.0.1:5060

    INVITE sip:0031123456789@10.14.0.1:5060SIP/2.0.

    Record-Route: <sip:10.14.0.2;lr=on>.

    Record-Route: <sip:10.14.0.3;lr=on>.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

    Max-Forwards: 68.

    Contact:
    <sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>.

    To: <sip:0031123456789@10.14.0.3:5060>.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 INVITE.

    Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER,
    INFO, MESSAGE.

    Content-Type: application/sdp.

    User-Agent: Bria 4 release 4.2.1 stamp 78100.

    Content-Length: 431.



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 100 trying -- your call is important to us.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

    To: <sip:0031123456789@10.14.0.3:5060>.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 INVITE.

    Server: kamailio (4.3.4 (x86_64/linux)).

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.0.0.1:5060

    INVITE sip:0031123456789@10.0.0.1:5060SIP/2.0.

    Record-Route: <sip:10.14.0.1;lr=on>.

    Record-Route: <sip:10.14.0.2;lr=on>.

    Record-Route: <sip:10.14.0.3;lr=on>.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

    Max-Forwards: 67.

    Contact:
    <sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>.

    To: <sip:0031123456789@10.14.0.3:5060>.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 INVITE.

    Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER,
    INFO, MESSAGE.

    Content-Type: application/sdp.

    User-Agent: Bria 4 release 4.2.1 stamp 78100.

    Content-Length: 431.



    #

    U 10.0.0.1:5060 -> 10.14.0.1:5060

    SIP/2.0 100 Trying.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0.

    Via: SIP/2.0/UDP
    10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To: <sip:0031123456789@10.14.0.3:5060>.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.2:5060 -> 10.14.0.1:5060

    CANCEL sip:0031123456789@10.14.0.1:5060SIP/2.0.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    Max-Forwards: 68.

    To: <sip:0031123456789@10.14.0.3:5060>.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 CANCEL.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.0.0.1:5060

    CANCEL sip:0031123456789@10.0.0.1:5060SIP/2.0.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    Max-Forwards: 67.

    To: <sip:0031123456789@10.14.0.3:5060>.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 CANCEL.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 200 canceling.

    Via: SIP/2.0/UDP
    10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-52bb.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 CANCEL.

    Server: kamailio (4.3.4 (x86_64/linux)).

    Content-Length: 0.

    .



    #

    U 10.0.0.1:5060 -> 10.14.0.1:5060

    SIP/2.0 200 OK.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To: <sip:0031123456789@10.14.0.3:5060>.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 CANCEL.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.0.0.1:5060 -> 10.14.0.1:5060

    SIP/2.0 487 Request Cancelled.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.0.0.1:5060

    ACK sip:0031123456789@10.0.0.1:5060SIP/2.0.

    Via: SIP/2.0/UDP
    10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0.

    Max-Forwards: 67.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    From:
    "+31612345678"<sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    CSeq: 2 ACK.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 487 Request Cancelled.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 487 Request Cancelled.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 487 Request Cancelled.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    #

    U 10.14.0.1:5060 -> 10.14.0.2:5060

    SIP/2.0 487 Request Cancelled.

    From: "+31612345678"
    <sip:+31612345678@10.14.0.3:5060>;tag=1f15682a.

    To:
    <sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10.

    Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI.

    Contact: <sip:10.0.0.1:5060>.

    CSeq: 2 INVITE.

    Server: sbc_5.

    Content-Length: 0.

    .



    *From:*sr-users [mailto:sr-users-bounces@lists.sip-router.org]
    *On Behalf Of *Daniel-Constantin Mierla
    *Sent:* Monday, March 14, 2016 2:44 PM
    *To:* Kamailio (SER) - Users Mailing List
    <sr-users@lists.sip-router.org
    <mailto:sr-users@lists.sip-router.org>>
    *Subject:* Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no
    via found in reply



    Hello,

    what would be relevant here is seeing the INVITE request sent
    to 10.14.0.1:5060 -- paste it to the mailing list discussion.
    That is going to be used to generate 487, and the Via stack
    from it should be used there.

    Cheers,
    Daniel

    On 14/03/16 13:23, Grant Bagdasarian wrote:

        Hello,



        We’re testing kamailio 4.3.4 with two kamailio’s
        communicating with each other. One of them is a gateway
        with rtpengine at the carrier side, the other is a basic
        sip router.

        When calling a destination and cancelling the INVITE a 487
        is received from the carrier and directly ACK’d by the
        first kamailio and in turn is forwarded to the second.

        But the 487 response received by the 2^nd kamailio doesn’t
        have a Via header which results in kamailio printing the
        error: receive_msg(): no via found in reply.



        Any ideas why the forwarded 487 doesn’t contain a Via
        header and how to fix this?



        Note: IP’s are changed.



        Carrier: 10.0.0.1

        Kamailio 1: 10.14.0.1

        Kamailio 2: 10.14.0.2



        U 10.0.0.1:5060 -> 10.14.0.1:5060

        SIP/2.0 487 Request Cancelled.

        Via: SIP/2.0/UDP
        10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

        From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
        <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

        To: <sip:003112345678@10.14.0.3:5060>
        <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

        Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

        Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

        CSeq: 2 INVITE.

        Server: sbc_5.

        Content-Length: 0.

        .



        #

        U 10.14.0.1:5060 -> 10.0.0.1:5060

        ACK sip:003112345678@10.0.0.1:5060SIP/2.0.

        Via: SIP/2.0/UDP
        10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0.

        Max-Forwards: 67.

        To: <sip:003112345678@10.14.0.3:5060>
        <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

        From: "+31612345678"<sip:+31612345678@10.14.0.3:5060>
        <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

        Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

        CSeq: 2 ACK.

        Content-Length: 0.

        .



        #

        U 10.14.0.1:5060 -> 10.14.0.2:5060

        SIP/2.0 487 Request Cancelled.

        From: "+31612345678" <sip:+31612345678@10.14.0.3:5060>
        <sip:+31612345678@10.14.0.3:5060>;tag=109ac722.

        To: <sip:003112345678@10.14.0.3:5060>
        <sip:003112345678@10.14.0.3:5060>;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10.

        Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU.

        Contact: <sip:10.0.0.1:5060> <sip:10.0.0.1:5060>.

        CSeq: 2 INVITE.

        Server: sbc_5.

        Content-Length: 0.




        _______________________________________________

        SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
        mailing list

        sr-users@lists.sip-router.org
        <mailto:sr-users@lists.sip-router.org>

        http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



    -- 

    Daniel-Constantin Mierla

    http://www.asipto.com

    http://twitter.com/#!/miconda
    <http://twitter.com/#%21/miconda>-
    http://www.linkedin.com/in/miconda

    Kamailio World Conference, Berlin, May 18-20, 2016 -
    http://www.kamailioworld.com



-- 

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda>-
http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 -
http://www.kamailioworld.com

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda http://twitter.com/#%21/miconda- http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

-- Daniel-Constantin Mierla http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Grant Bagdasarian

4 Apr 4 Apr

8:02 a.m.

Hi Daniel,

You mentioned below about this issue not being complaint with the RFC. Our supplier is telling us this is normal behavior and that they went through the RFC and found this was normal behavior.

If it's not too much work, could you tell me in which part of the RFC this is described?

Regards,

Grant

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Cheers, Daniel On 18/03/16 15:43, Grant Bagdasarian wrote: Hi Daniel,

No problem :)

Regards,

Grant

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel On 18/03/16 10:05, Grant Bagdasarian wrote: Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

Any ideas how to solve this?

Regards,

Grant ________________________________ From: sr-users <sr-users-bounces@lists.sip-router.orgmailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.commailto:miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

Cheers, Daniel On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

Any ideas why the forwarded 487 doesn't contain a Via header and how to fix this?

Note: IP's are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

_______________________________________________

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list

sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Daniel-Constantin Mierla

http://www.asipto.com

http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com

Olle E. Johansson

8:13 a.m.

...

On 04 Apr 2016, at 10:02, Grant Bagdasarian gb@cm.nl wrote:

Hi Daniel,

You mentioned below about this issue not being complaint with the RFC. Our supplier is telling us this is normal behavior and that they went through the RFC and found this was normal behavior.

If it’s not too much work, could you tell me in which part of the RFC this is described?

8.2.6.2 https://tools.ietf.org/html/rfc3261#section-8.2.6.2 Headers and Tags

The From field of the response MUST equal the From header field of the request. The Call-ID header field of the response MUST equal the Call-ID header field of the request. The CSeq header field of the response MUST equal the CSeq field of the request. The Via header field values in the response MUST equal the Via header field values in the request and MUST maintain the same ordering.

RFC 3261 basics.

...

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 4:33 PM To: Grant Bagdasarian <gb@cm.nl mailto:gb@cm.nl>; Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

the problem is that the device you interconnect with (Server: sbc_5) is not sending all the Via headers from INVITE in the 487 -- it is only one Via:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

Notice the 100 trying Via stack:

# U 10.0.0.1:5060 -> 10.14.0.1:5060

SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=1f15682a. To: sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

My guess that the sbc_5 is so poor implemented that it takes the Via from last request, which is CANCEL, but CANCEL is a hop-by-hop request in this case. If my guess is confirmed, the implementation of sbc_5 is really far away from RFC3261, something that I haven't probably seen since 2002/3.

To test, you can try to use forward() for CANCEL instead of t_relay(). But you need to know where to send it -- same address as for INVITE -- you can hardcode some values in config for sake of simplicity to test. A proper workaround can be built using htable module to store where the invite was sent, using call-id as a key.

Cheers, Daniel

On 18/03/16 15:43, Grant Bagdasarian wrote: Hi Daniel,

No problem J

Our devices are kamailios. Our customers use different equipment for sending traffic and I’m not sure what kind of equipment our carriers are using. So, I can’t really tell what device they’re using. My test was done using Bria (X-Lite) acting as a “customer”.

Regards,

Grant

From: Daniel-Constantin Mierla [mailto:miconda@gmail.com mailto:miconda@gmail.com] Sent: Friday, March 18, 2016 10:25 AM To: Grant Bagdasarian gb@cm.nl mailto:gb@cm.nl; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

with CeBIT trip this week, I didn't get the change to look too much at it...

What is the device sending the reply to INVITE?

Cheers, Daniel

On 18/03/16 10:05, Grant Bagdasarian wrote: Hello Community,

Could someone point me into the right direction for fixing this issue with CANCEL replies?

Regards,

Grant

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian Sent: Tuesday, March 15, 2016 8:47 PM To: 'miconda@gmail.com mailto:miconda@gmail.com' miconda@gmail.com mailto:miconda@gmail.com; Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Any ideas how to solve this?

Regards,

Grant From: sr-users <sr-users-bounces@lists.sip-router.org mailto:sr-users-bounces@lists.sip-router.org> on behalf of Grant Bagdasarian <gb@cm.nl mailto:gb@cm.nl> Sent: Monday, March 14, 2016 3:09:47 PM To: 'miconda@gmail.com mailto:miconda@gmail.com'; Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello Daniel,

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

I also removed the SDP from the INVITE and the 183 messages.

This is the trace from the Kamailio which directly communicates with the Carrier.

U 10.14.0.2:5060 -> 10.14.0.1:5060 INVITE sip:0031123456789@10.14.0.1:5060 sip:0031123456789@10.14.0.1:5060 SIP/2.0. Record-Route: <sip:10.14.0.2;lr=on sip:10.14.0.2;lr=on>. Record-Route: <sip:10.14.0.3;lr=on sip:10.14.0.3;lr=on>. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. Max-Forwards: 68. Contact: <sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89 sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE. Content-Type: application/sdp. User-Agent: Bria 4 release 4.2.1 stamp 78100. Content-Length: 431.

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Server: kamailio (4.3.4 (x86_64/linux)). Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 INVITE sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0. Record-Route: <sip:10.14.0.1;lr=on sip:10.14.0.1;lr=on>. Record-Route: <sip:10.14.0.2;lr=on sip:10.14.0.2;lr=on>. Record-Route: <sip:10.14.0.3;lr=on sip:10.14.0.3;lr=on>. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. Max-Forwards: 67. Contact: <sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89 sip:10.14.0.3;line=sr-1sX9bA20uS8PuS8NWSFPWUiPW0IRuS8RuJHNuQ4KuQ89>. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 INVITE. Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, MESSAGE. Content-Type: application/sdp. User-Agent: Bria 4 release 4.2.1 stamp 78100. Content-Length: 431.

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bK3c3b.9cad3c629aa5c2985e543c285f2f6d1d.0. Via: SIP/2.0/UDP 10.14.0.3;branch=z9hG4bKsr-jNXap0IRuJngh6iFuS1xpYUspYiRWQikWSisuQfjcQKOM-8C8odTwzW4V-4LMU1N8O2fWSINuYFmpSUfpcKXuq8NW0is8YdObqasuQuP. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.2:5060 -> 10.14.0.1:5060 CANCEL sip:0031123456789@10.14.0.1:5060 sip:0031123456789@10.14.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. Max-Forwards: 68. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 CANCEL sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Max-Forwards: 67. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 200 canceling. Via: SIP/2.0/UDP 10.14.0.2;branch=z9hG4bK3c3b.6002c178e1a0751f80857e10c4caeb35.0. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-52bb. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Server: kamailio (4.3.4 (x86_64/linux)). Content-Length: 0. .

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 CANCEL. Server: sbc_5. Content-Length: 0. .

# U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:0031123456789@10.0.0.1:5060 sip:0031123456789@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK3c3b.a6603e0f92db305f775f8bf1d95dc7d9.0. Max-Forwards: 67. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. From: "+31612345678"<sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. CSeq: 2 ACK. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" <sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060>;tag=1f15682a. To: <sip:0031123456789@10.14.0.3:5060 sip:0031123456789@10.14.0.3:5060>;tag=sbcsipuas_1_C52464_20160314100333554_b12sb10. Call-ID: 78100ZGIyZGM2ZTY4ODM4YWZlZGFjNTBjMDZmYjQzMzBkOGI. Contact: <sip:10.0.0.1:5060 sip:10.0.0.1:5060>. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, March 14, 2016 2:44 PM To: Kamailio (SER) - Users Mailing List <sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

Hello,

what would be relevant here is seeing the INVITE request sent to 10.14.0.1:5060 -- paste it to the mailing list discussion. That is going to be used to generate 487, and the Via stack from it should be used there.

Cheers, Daniel

On 14/03/16 13:23, Grant Bagdasarian wrote: Hello,

We’re testing kamailio 4.3.4 with two kamailio’s communicating with each other. One of them is a gateway with rtpengine at the carrier side, the other is a basic sip router. When calling a destination and cancelling the INVITE a 487 is received from the carrier and directly ACK’d by the first kamailio and in turn is forwarded to the second. But the 487 response received by the 2nd kamailio doesn’t have a Via header which results in kamailio printing the error: receive_msg(): no via found in reply.

Any ideas why the forwarded 487 doesn’t contain a Via header and how to fix this?

Note: IP’s are changed.

Carrier: 10.0.0.1 Kamailio 1: 10.14.0.1 Kamailio 2: 10.14.0.2

U 10.0.0.1:5060 -> 10.14.0.1:5060 SIP/2.0 487 Request Cancelled. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.0.0.1:5060 ACK sip:003112345678@10.0.0.1:5060 sip:003112345678@10.0.0.1:5060 SIP/2.0. Via: SIP/2.0/UDP 10.14.0.1;branch=z9hG4bK8e28.642c68037d059634308d4be8fe3f0cdc.0. Max-Forwards: 67. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. From: "+31612345678"sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. CSeq: 2 ACK. Content-Length: 0. .

# U 10.14.0.1:5060 -> 10.14.0.2:5060 SIP/2.0 487 Request Cancelled. From: "+31612345678" sip:+31612345678@10.14.0.3:5060 sip:+31612345678@10.14.0.3:5060;tag=109ac722. To: sip:003112345678@10.14.0.3:5060 sip:003112345678@10.14.0.3:5060;tag=sbcsipuas_1_C22196_20160314080307791_b59sb10. Call-ID: 78100MjY3OGExZmMyODU2MzAyMzM5ODA3MmNhMDdlMzg0MzU. Contact: sip:10.0.0.1:5060 sip:10.0.0.1:5060. CSeq: 2 INVITE. Server: sbc_5. Content-Length: 0.

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com http://www.kamailioworld.com/

-- Daniel-Constantin Mierla http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com http://www.kamailioworld.com/

-- Daniel-Constantin Mierla http://www.asipto.com http://www.asipto.com/ http://twitter.com/#!/miconda http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda http://www.linkedin.com/in/miconda Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com http://www.kamailioworld.com/_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Olle E. Johansson

8:16 a.m.

...

On 04 Apr 2016, at 10:02, Grant Bagdasarian gb@cm.nl wrote:

Hi Daniel,

You mentioned below about this issue not being complaint with the RFC. Our supplier is telling us this is normal behavior and that they went through the RFC and found this was normal behavior.

If it’s not too much work, could you tell me in which part of the RFC this is described?

8.2.6.2 Headers and Tags

RFC 3261 basics. The UAS copies ALL Via:s from the request into the response. This is how we route responses through a SIP network, so without all headers, communication will likely be very broken.

...

Grant Bagdasarian

8:57 a.m.

Thank you Olle! I’ll discuss this with our supplier.

From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Monday, April 4, 2016 10:16 AM To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio 4.3.4: receive_msg(): no via found in reply

On 04 Apr 2016, at 10:02, Grant Bagdasarian <gb@cm.nlmailto:gb@cm.nl> wrote:

Hi Daniel,

You mentioned below about this issue not being complaint with the RFC. Our supplier is telling us this is normal behavior and that they went through the RFC and found this was normal behavior.

If it’s not too much work, could you tell me in which part of the RFC this is described?

8.2.6.2 Headers and Tags

RFC 3261 basics. The UAS copies ALL Via:s from the request into the response. This is how we route responses through a SIP network, so without all headers, communication will likely be very broken.

Mikko Lehto

14 Aug 14 Aug

12:30 p.m.

New subject: Fix missing Via with t_reply() (was: Kamailio 4.3.4: receive_msg(): no via found in reply)

2016-03-18 Daniel-Constantin Mierla miconda@gmail.com wrote:

...

My guess that the sbc_5 is so poor implemented that it takes the Via from last request, which is CANCEL, but CANCEL is a hop-by-hop request in this case. If my guess is confirmed, the implementation of sbc_5 is really far away from RFC3261, something that I haven't probably seen since 2002/3.

To test, you can try to use forward() for CANCEL instead of t_relay(). But you need to know where to send it -- same address as for INVITE -- you can hardcode some values in config for sake of simplicity to test. A proper workaround can be built using htable module to store where the invite was sent, using call-id as a key.

Hi Grant, Daniel

I accidentally found this 2016 thread and wanted to share my different solution.

I ran into similar issue: 487 reply from SIP phone UA came with insufficient Via headers after CANCEL. In fact situation looked exactly like described above: Via stack for reply to INVITE seem to be taken incorrectly from CANCEL. I did not observe any errors from Kamailio, but Asterisk chan_sip (original INVITE sender) spits: --- parse_via: received request without a Via header handle_incoming: Dropping this SIP message with Call-ID 'abc', it's incomplete ---

My quick solution was to reply locally with t_reply() when branch with missing second via was winning: --- ...usrloc lookup()... +t_on_branch_failure("TOUSER"); t_on_failure("FAILURE_TOUSER"); route(RELAY);

+event_route[tm:branch-failure:TOUSER] +{ + # Save branch ruid if broken Via detected + # If this branch wins, Via will be "fixed" with local reply + if ( $T_rpl($sel(via[2])) == $null ) $avp(secondviamissing) = $T(ruid); +} + failure_route[FAILURE_TOUSER] { + if ( $avp(secondviamissing) != $null && $avp(secondviamissing) == $T(ruid) ) + { + # Some UAs (VP530P 23.70.74.5) seem to copy Via stack from CANCEL + # Lets "add" missing Via by creating internal reply + append_to_reply("X-log: viafix\r\n"); + t_reply("$T(reply_code)", "$T_reply_reason"); + exit; + } } ---

That seems to do the trick, at least in simple non-branching case.

What do you think? (other than using single $avp(secondviamissing) for whole transaction...)

-- Mikko

Daniel-Constantin Mierla

15 Aug 15 Aug

7:36 a.m.

New subject: Fix missing Via with t_reply()

Hello,

On 14.08.17 14:30, Mikko Lehto wrote:

...

2016-03-18 Daniel-Constantin Mierla miconda@gmail.com wrote:

...
My guess that the sbc_5 is so poor implemented that it takes the Via from last request, which is CANCEL, but CANCEL is a hop-by-hop request in this case. If my guess is confirmed, the implementation of sbc_5 is really far away from RFC3261, something that I haven't probably seen since 2002/3.

To test, you can try to use forward() for CANCEL instead of t_relay(). But you need to know where to send it -- same address as for INVITE -- you can hardcode some values in config for sake of simplicity to test. A proper workaround can be built using htable module to store where the invite was sent, using call-id as a key.

Hi Grant, Daniel

I accidentally found this 2016 thread and wanted to share my different solution.

I ran into similar issue: 487 reply from SIP phone UA came with insufficient Via headers after CANCEL. In fact situation looked exactly like described above: Via stack for reply to INVITE seem to be taken incorrectly from CANCEL. I did not observe any errors from Kamailio, but Asterisk chan_sip (original INVITE sender) spits:

parse_via: received request without a Via header handle_incoming: Dropping this SIP message with Call-ID 'abc', it's incomplete

My quick solution was to reply locally with t_reply() when branch with missing second via was winning:

...usrloc lookup()... +t_on_branch_failure("TOUSER"); t_on_failure("FAILURE_TOUSER"); route(RELAY);

+event_route[tm:branch-failure:TOUSER] +{

# Save branch ruid if broken Via detected

# If this branch wins, Via will be "fixed" with local reply

if ( $T_rpl($sel(via[2])) == $null ) $avp(secondviamissing) = $T(ruid);

+}

failure_route[FAILURE_TOUSER] {
if ( $avp(secondviamissing) != $null && $avp(secondviamissing) == $T(ruid) )

{
   # Some UAs (VP530P 23.70.74.5) seem to copy Via stack from CANCEL
   # Lets "add" missing Via by creating internal reply
   append_to_reply("X-log: viafix\r\n");
   t_reply("$T(reply_code)", "$T_reply_reason");
   exit;
}
}

That seems to do the trick, at least in simple non-branching case.

What do you think? (other than using single $avp(secondviamissing) for whole transaction...)

Could be a workaround, indeed.

But I guess you can do it directly in the failure_route, without event_route, testing if the reply has a second via there and using t_reply() if not.

Cheers, Daniel

-- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

2748

Age (days ago)

3267

Last active (days ago)

sr-users@lists.kamailio.org

16 comments

4 participants

tags (0)

participants (4)

Daniel-Constantin Mierla
Grant Bagdasarian
Mikko Lehto
Olle E. Johansson