[SR-Users] UPDATE relayed from wrong socket

Sergiu Pojoga pojogas at gmail.com
Thu Oct 11 21:03:23 CEST 2018


Hi ppl,

I have this problem with call transfer, may be someone can help.

The phone to the far right is registered with the Registrar to the far left
using two PATH headers (trespassing two proxy ports, 5070 then 5060).

As you can see in the graph below, after receiving the UPDATE request,
Kamailio relays it further from port 5060, I expect it to be from 5070 just
like the dialog forming INVITE and the CANCEL afterwards.

[image: image.png]

The UPDATE has a to-tag, but unlike the original INVITE - it has no Route
header!???

route[*WITHINDLG*] {
if (!has_totag()) return;
if (loose_route()) {
route(DLGURI);
if (is_method("BYE")) {

...

}
else if ( is_method("ACK") ) {
route(NATMANAGE);
}
else if ( is_method("NOTIFY") ) {
record_route();
}

route(RELAY);
exit;
}

if ( is_method("ACK") ) {

...

}

# handle UPDATE method for in-dialog requests
if (is_method("*UPDATE*")) {
route(DLGURI);
record_route();
route(RELAY);
}
}

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20181011/c3bbffa7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 20978 bytes
Desc: not available
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20181011/c3bbffa7/attachment.png>


More information about the sr-users mailing list