[sr-dev] [kamailio/kamailio] loose route cannot be completed when kamailio inserts two Record-Route headers (#1215)

sergey-safarov notifications at github.com
Sun Aug 13 22:14:40 CEST 2017


### Description

When kamailio need to pass call from carrier to customer VoIP PBX in docker container on swarm cluster then it not possible.
Network interconnection.
In docker environment eth1 NIC of kamailio and VoIP PBX connected to internet via iptables masquerading. eth1 NIC of kamailio and VoIP PBX have random IP address and generally no way to pass message between kamailio and VoIP PBX via eth1 NIC.
Also both containers have eth0 NIC in same network with static IP. But network on eth0 NIC not connected to Internet. 

SIP signaling is passed like
eth1-Kamailio-eth0 <-> eth0-VoIP PBX

In this network kamailio add/removes two Record-Route.  For ACK message with two `Route` headers this rule does not work. Each `Route` headers for same kamailio instance and must be translated by one loose_route call
```
The proxy will inspect the URI in the topmost Route header
          field value.  If it indicates this proxy, the proxy removes it
          from the Route header field (this route node has been
          reached).
```
Really `Route` headers translated separately and second `loose_route` cannot be completed. Details in `details.txt`
[details.txt](https://github.com/kamailio/kamailio/files/1220872/details.txt)

Wireshark pcap file and kamailio log with enabled debug attached of similar calls is attached.
[full-call.zip](https://github.com/kamailio/kamailio/files/1220875/full-call.zip)

#### Reproduction

Create config when kamailio add two `Record-Route` headers and send ACK with two `Route` headers

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1215
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20170813/00cc120e/attachment-0001.html>


More information about the sr-dev mailing list