[SR-Users] topoh and onhold reinvites

[Daniel-Constantin Mierla]

Hello,

the re-INVITE should be handled in the same way as ACK for 200ok or BYE 
(i.e., request within dialog). Do you get any error message in syslog? 
Can you share a ngrep trace of such situation (from initial INVITE to 
the end)? you can send it to me if it has sensitive information.

Cheers,
Daniel

On 09/04/14 16:06, Daniel Tryba wrote:
> I'm having some trouble with kamailio that uses the topology hider module and
> an incoming call being put onhold by the caller. The INVITE containing the sdp
> a=sendonly is to the 172.19.162.1 (the topoh mask_ip) contact header from the
> 200 OK to the initial INVITE.
>
> U 109.235.36.178:5060 -> 109.235.32.40:5060
> INVITE sip:172.19.162.1:5060;line=pcs-
> mp4KWiTsxRmtEAM3WGysx7y3xGnoxAxtuAxSuA7KEsktxGZKWgQfZD6smqlf9Gttzjy*;user=phone
> SIP/2.0.
>
> This is handled within dialog (has_totag() && !loose_route()), which in the
> default config ends in a sl_send_reply("404","Not here")
>
> Explicitly handing INVITE (just relaying), results in the INVITE being sent to
> 172.19.162.1 (which doesn't exist)
>
> U 109.235.32.40:5060 -> 172.19.162.1:5060
> INVITE sip:172.19.162.1:5060;line=pcs-
> mp4KWiTsxRmtEAM3WGysx7y3xGnoxAxtuAxSuA7KEsktxGZKWgQfZD6smqlf9Gttzjy*;user=phone
> SIP/2.0.
>
> How to get this INVITE to the actual destination? To get the same result for
> the INVITE as for the ACK to the 200 OK?
>
> U 109.235.32.40:5060 -> 109.235.36.178:5060
> SIP/2.0 200 OK.
> ...
> Contact: <sip:172.19.162.1;line=pcs-
> mp4KWiTsxRmtEAM3WGysx7y3xGnoxAxtuAxSuA7KEsktxGZKWgQfZD6smqlf9Gttzjy*>.
>
> U 109.235.36.178:5060 -> 109.235.32.40:5060
> ACK sip:172.19.162.1;line=pcs-
> mp4KWiTsxRmtEAM3WGysx7y3xGnoxAxtuAxSuA7KEsktxGZKWgQfZD6smqlf9Gttzjy* SIP/2.0.
>
> U 109.235.32.40:5060 -> 109.235.34.107:5060
> ACK sip:+31756418030 at 109.235.34.107:5060;transport=udp SIP/2.0.
>
>

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda