30 Nov
2018
30 Nov
'18
5:59 p.m.
Hi all,
I’m having some issues with ACK’s.
Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint, Kamailio
is adding a second Via header - which isn’t valid as per RFC 3261 (17.1.1.3);
“The ACK MUST contain a single Via header field, and this MUST be equal to the top Via
header field of the original request."
Endpoints are registered with Kamailio but INVITES are routed via Asterisk for dial plan
and media reasons.
I’m running fairly bog-standard Kamailio and Asterisk installs.
I’ve attached a sample PCAP for if anyone has any suggestions.
Thanks.
Dan
30 Nov
30 Nov
6:10 p.m.
Hi,
Note that there are two different kinds of ACKs. An ACK for a 2xx
transaction is an in-dialog request that follows the rules for Section
13, and having two Via hops in one of those is entirely appropriate.
On Fri, Nov 30, 2018 at 02:59:52PM +0000, Dan Quinney wrote:
Hi all,
I’m having some issues with ACK’s.
Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint, Kamailio
is adding a second Via header - which isn’t valid as per RFC 3261 (17.1.1.3);
“The ACK MUST contain a single Via header field, and this MUST be equal to the top Via
header field of the original request."
Endpoints are registered with Kamailio but INVITES are routed via Asterisk for dial plan
and media reasons.
I’m running fairly bog-standard Kamailio and Asterisk installs.
I’ve attached a sample PCAP for if anyone has any suggestions.
Thanks.
Dan
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
6:47 p.m.
Hi Alex,
Thanks for that, I’ve been reading the RFC but clearly missed the bit about section 13.
Dan
On 30 Nov 2018, at 15:10, Alex Balashov
<abalashov(a)evaristesys.com> wrote:
Hi,
Note that there are two different kinds of ACKs. An ACK for a 2xx
transaction is an in-dialog request that follows the rules for Section
13, and having two Via hops in one of those is entirely appropriate.
On Fri, Nov 30, 2018 at 02:59:52PM +0000, Dan Quinney wrote:
Hi all,
I’m having some issues with ACK’s.
Specifically, when an ACK reaches Kamailio from either Asterisk or an endpoint, Kamailio
is adding a second Via header - which isn’t valid as per RFC 3261 (17.1.1.3);
“The ACK MUST contain a single Via header field, and this MUST be equal to the top Via
header field of the original request."
Endpoints are registered with Kamailio but INVITES are routed via Asterisk for dial plan
and media reasons.
I’m running fairly bog-standard Kamailio and Asterisk installs.
I’ve attached a sample PCAP for if anyone has any suggestions.
Thanks.
Dan
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 <tel:+1-706-510-6800> / +1-800-250-5920
<tel:+1-800-250-5920> (toll-free)
Web: http://www.evaristesys.com/ <http://www.evaristesys.com/>,
http://www.csrpswitch.com/ <http://www.csrpswitch.com/>
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
2189
days inactive
2189
days old
2 comments
2 participants
participants (2)
-
Alex Balashov -
Dan Quinney