Hello,
you hve to provide the sip traffic for this case, the screenshot doesn't
show the sip headers used for routing in this case, therefore grab the
sip traffic for all sip messages in such scenarion, either ngrep output
or pcap file, and send it over to see if some headers are missing or not
set properly.
Cheers,
Daniel
On 11.10.18 21:03, Sergiu Pojoga wrote:
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.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.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla --
www.asipto.com
www.twitter.com/miconda --
www.linkedin.com/in/miconda
Kamailio World Conference --
www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin --
www.asipto.com