[sr-dev] [tracker] Task opened: Incorrect outbound interface used in Via and Record-Route (Attachment added)

sip-router bugtracker at sip-router.org
Thu Jul 5 17:41:14 CEST 2012


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - Hugh Waite (hugh.waite) 

Attached to Project - sip-router
Summary - Incorrect outbound interface used in Via and Record-Route
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 3.3
Due in Version - Undecided
Due Date - Undecided
Details - I am using the recent advertised_address feature of kamailio 3.3 to bridge signalling across different network interfaces.

I have these lines in my config (in this order; eth0 and eth1 respectively):

listen 192.168.0.61 advertise 192.168.0.75:5060
listen 192.168.10.61 advertise 192.168.10.75:5060

When a call comes in on .10.61 and is sent on .0.61 (eth1 -> eth0) a double record-route is inserted and the correct advertised addresses are used (.10.75 and .0.75). This is correct and a BYE sent from the called client works.
When a call comes in on .0.61 and is sent to .10.61 (eth0 -> eth1) only one record-route header is inserted which contains .0.75 (eth0). This prevents the called client from sending within-dialog requests because the first route header is on the wrong network. The Via also contains the .0.75 address.

Even stranger, if I swap the two 'listen' lines in my config, kamailio inserts a double rr header with both advertised addresses even when sending requests from eth0 to eth0, also causing within dialog requests to fail.

Does kamailio always pick the first interface for the outbound rr?

I have tried to work around this by using set_advertised_address("192.168.10.75") is various places, but this seems to only affects the Via header.

One or more files have been attached.

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=241

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the sr-dev mailing list