sorted this out. but slightly hackish
i treated 180 the same as 100 to prevent it from getting the to-tag
setStatus(Proceeding);
instead of
setStatus(Early);
Kelvin Chua
---------- Forwarded message ----------
From: Kelvin Chua <[email protected]>
Date: Thu, Oct 30, 2014 at 11:28 PM
Subject: To-tag changes
To: "[email protected]" <[email protected]>
I have a peculiar situation, where the to-tag changes, and when this
happens, sems refuse to relay.
consider this situation.
UA sends invite, sems relay, kamailio sends back fake ring
(sl_send_reply("180","Ringing")), kamailio sends call to egress.
when sems receive fake ring, it saves the to-tag. when egress sends back
his own 180/183 and kamailio relays it to sems, sems will complain that
[#7f7b131f1700/30229] [onSipReply, AmB2BSession.cpp:470] DEBUG: sess
0x7f7b0400bbb0 received 183 reply with != to-tag: gK08fadec4
(remote-tag:c3b5495ce7a238806d8d1b36f1583276-36de)
it then refuses to relay this, sort of just stopped stopped there.
i just need sems to relay that to the A leg. is there an easy way to fix
this?
Kelvin Chua
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
