[sr-dev] [tracker] Task opened: maddr broken in 4.1.x?

sip-router bugtracker at sip-router.org
Wed May 21 10:59:06 CEST 2014


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

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

User who did this - Morten Tryfoss (mtryfoss) 

Attached to Project - sip-router
Summary - maddr broken in 4.1.x?
Task Type - Bug Report
Category - tm
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - maddr is used in all lync-setups.

Kamailio 4.1.1 receives this, which should be forwarded:
PRACK sip:med002.lync4all.intra:5060;transport=Tcp;maddr=<publicip>

And returns this error when using t_relay():
May 20 22:59:19 sip3ha /usr/sbin/kamailio[24754]: ERROR: <core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "med002.lync4all.intra"
May 20 22:59:19 sip3ha /usr/sbin/kamailio[24754]: ERROR: tm [ut.h:337]: uri2dst2(): failed to resolve "med002.lync4all.intra"
May 20 22:59:19 sip3ha /usr/sbin/kamailio[24754]: ERROR: tm [t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches

It seems like it worked in 3.3.x.


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

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