Hello,
On 21/01/14 13:23, Keith wrote:
Hi,
Thanks for the replies so far, good news is I got it working by
switching off mhomed (mhomed=0). However this seems to have broken my
dispatcher as the SIP OPTIONS probing is being sent from the wrong
interface!
Any ideas how to set where dispatch
Hi All,
Thanks for all the advice, I managed to sort this one (I hope!). For anyone
else interested I had to add some code at the start of the routing to look
for a SIP UPDATE request. If it was a request then to set the $fs (forced
socket) value to equal $Ri (Received interface) value.
Once this
Hi,
Thanks for the replies so far, good news is I got it working by switching
off mhomed (mhomed=0). However this seems to have broken my dispatcher as
the SIP OPTIONS probing is being sent from the wrong interface!
Any ideas how to set where dispatcher sends these from??
Cheers
Keith
__
On 20.01.2014 17:48, Keith wrote:
Hi,
I have a kamailio server which is responding to SIP updates but sending
from the wrong IP. I have multiple IPs in the same subnet on the same
NIC. Is there anyway to say send update back out of the interface it was
received on?
I think that should be don
Hello,
can you provide ngrep out put for such call, including the initial
INVITE and its responses? Like:
ngrep -d any -qt -W byline port 5060
I have to check if there is double record routing and if the sockets are
selected accordingly.
Cheers,
Daniel
On 21/01/14 10:12, Keith wrote:
Hi
Hi Daniel,
So I have looked at the packet capture, the "SIP Request: UPDATE" comes in
but when that request is forwarded to the phone it sends it from the
interface IP and not the sub interface IP. Therefore the message never gets
to the phone and the call is hung up after 30 seconds (due to the f
Hello,
what do you mean by SIP updates? The UPDATE request should not be
handled by kamailio, it should be forwarded.
In general, for forcing a socket, you can use force_send_scoket(...) or
set the socket value to $fs.
Cheers,
Daniel
On 20/01/14 17:48, Keith wrote:
Hi,
I have a kamailio
