<div dir="ltr">Hi,<div>looking at the trace, it seems to me that the 407 is not sent by Kamailio but by the FS1 server ("<span style="font-family:arial,sans-serif;font-size:14px">User-Agent: IMX" in the 407, as for the 1st 407 sent by FS2), and that you are probably missing in the trace the messages between Kamailio and FS1.</span></div><div><span style="font-family:arial,sans-serif;font-size:14px">If this is the case you could either:</span></div><div><span style="font-family:arial,sans-serif;font-size:14px">- disable the authentication in freeswitch if you don't need it</span></div><div><span style="font-family:arial,sans-serif;font-size:14px">- store the custom header when receiving the 302 and use it to set $du upon receiving the 2nd INVITE</span></div><div><font face="arial, sans-serif"><span style="font-size:14px">For the latter you can have several solutions, I suggest you to have a a look at the htable module. For example you could use it to store the key USERID::CALLID with the value of your custom header and retrieve it when you receive the authenticated INVITE from the client. Something like</span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px"><br></span></font></div><div><font face="arial, sans-serif"><span style="font-size:14px">sht(TABLE_NAME=>$fU::$ci) = </span></font><span style="font-family:arial,sans-serif;font-size:14px">$avp(imx-redirect);</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">to store it, and then</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">$avp(imx-redirect) = </span><span style="font-family:arial,sans-serif;font-size:14px">sht(TABLE_NAME=>$fU::$ci)</span><span style="font-family:arial,sans-serif;font-size:14px">;</span><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">to retrieve it.</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">Hope this helps.</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">CHeers,</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:14px">Federico</span></div><div><span style="font-family:arial,sans-serif;font-size:14px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 16, 2014 at 3:28 AM, Nicholas Gill <span dir="ltr"><<a href="mailto:nick@etellicom.com" target="_blank">nick@etellicom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 15/09/14 16:03, Federico Cabiddu wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What happens if you call t_relay() after setting $du?<br>
</blockquote></span>
Same result. Kamailio sends 407 to caller, which then creates a new INVITE.<br>
<br>
I suspect my configuration doesn't reflect the intent, so I'm adding it below along with other particulars of the test environment.<br>
<br>
Is there a specific way to cause kamailio to relay the INVITE to a particular server based on a dynamic variable?<br>
<br>
Cheers,<br>
<br>
-nick<br>
<br>
192.168.20.215 - Caller<br>
<a href="http://192.168.20.214:5060" target="_blank">192.168.20.214:5060</a> Kamailio (<a href="http://node1.etellicom.com" target="_blank">node1.etellicom.com</a>)<br>
<a href="http://192.168.20.214:5080" target="_blank">192.168.20.214:5080</a> FS1 (<a href="http://node1.etellicom.com" target="_blank">node1.etellicom.com</a>)<br>
<a href="http://192.168.20.198:5080" target="_blank">192.168.20.198:5080</a> FS2 (<a href="http://node2.etellicom.com" target="_blank">node2.etellicom.com</a>)<br>
<br>
Kamailio:<br>
<br>
version: kamailio 4.1.5 (x86_64/linux) 2b3d4b<br>
<br>
Configuration diff from default:<br>
<br>
*** kamailio.cfg.default    2014-08-29 15:07:42.336496172 +1000<br>
--- kamailio.cfg    2014-09-16 10:43:50.199400261 +1000<br>
*************** loadmodule "xmlrpc.so"<br>
*** 283,288 ****<br>
--- 283,296 ----<br>
  loadmodule "debugger.so"<br>
  #!endif<br>
<br>
+ loadmodule "dispatcher.so"<br>
+ modparam("dispatcher", "flags", 2)<br>
+ modparam("dispatcher", "list_file", "/root/dispatcher.list")<br>
+ modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")<br>
+ modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")<br>
+ modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")<br>
+ #modparam("dispatcher", "ds_ping_interval", 60)<br>
+<br>
  # ----------------- setting module-specific parameters ---------------<br>
<br>
<br>
*************** request_route {<br>
*** 491,496 ****<br>
--- 499,509 ----<br>
          setflag(FLT_ACC); # do accounting<br>
      }<br>
<br>
+     if(!ds_is_from_list("1"))<br>
+     {<br>
+         route(DISPATCH);<br>
+     }<br>
+<br>
      # dispatch requests to foreign domains<br>
      route(SIPOUT);<br>
<br>
*************** request_route {<br>
*** 516,521 ****<br>
--- 529,576 ----<br>
      route(LOCATION);<br>
  }<br>
<br>
+ # Dispatch requests<br>
+ route[DISPATCH] {<br>
+<br>
+     # Hash over to uri for test purposes<br>
+     if(!ds_select_dst("1", "2"))<br>
+     {<br>
+         send_reply("404", "No destination");<br>
+         exit;<br>
+     }<br>
+     xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n");<br>
+     t_on_failure("RTF_DISPATCH");<br>
+     route(RELAY);<br>
+     exit;<br>
+ }<br>
+<br>
+ # Dispatch failure route<br>
+ failure_route[RTF_DISPATCH] {<br>
+     if (t_is_canceled()) {<br>
+         exit;<br>
+     }<br>
+     # next DST - only for 500 or local timeout<br>
+     if (t_check_status("500")<br>
+             or (t_branch_timeout() and !t_branch_replied()))<br>
+     {<br>
+         if(ds_next_dst())<br>
+         {<br>
+             t_on_failure("RTF_DISPATCH");<br>
+             route(RELAY);<br>
+             exit;<br>
+         }<br>
+     }<br>
+<br>
+     if ($avp(imx-redirect) != $null)<br>
+     {<br>
+         $du = $avp(imx-redirect);<br>
+         xlog("SCRIPT: REDIRECT: going to <$ru> via <$du>\n");<br>
+ #        route(RELAY);<br>
+         t_relay();<br>
+         exit;<br>
+     }<br>
+<br>
+ }<br>
<br>
  route[RELAY] {<br>
<br>
*************** onreply_route[MANAGE_REPLY] {<br>
*** 911,916 ****<br>
--- 966,977 ----<br>
      xdbg("incoming reply\n");<br>
      if(status=~"[12][0-9][0-9]")<br>
          route(NATMANAGE);<br>
+<br>
+     if (t_check_status("3[0-9][0-9]") and is_present_hf("X-imx-redirect"<u></u>))<br>
+     {<br>
+         $avp(imx-redirect) = $hdr(X-imx-redirect);<br>
+         xlog("SCRIPT: REDIRECT, Store avp for redirect: $avp(imx-redirect)\n");<br>
+     }<br>
  }<br>
<br>
  # manage failure routing cases<br>
<br>
<br>
SIP trace of call intended to be redirected to a specific server.<br>
<br>
Scenario starts with normal INVITE, 100, proxy auth from backend server, INVITE with auth.<br>
When FS2 receives the authenticated invite, it responds with 302 and indicates via the X-imx-redirect header to redirect the request to FS1.<br>
<br>
Then I want to send the INVITE to the given server by setting $du and calling t_relay() but my current configuration seems to cause kamailio to respond to the caller with 407 instead.<br>
<br>
<br>
10:46:27.361991 IP 192.168.20.215.5062 > 192.168.20.214.5060<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 70<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<br>
<br>
10:46:27.362567 IP 192.168.20.214.5060 > 192.168.20.215.5062<br>
SIP/2.0 100 trying -- your call is important to us<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
Server: kamailio (4.1.5 (x86_64/linux))<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.362745 IP 192.168.20.214.5060 > 192.168.20.198.5080<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Record-Route: <sip:192.168.20.214;lr=on><br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bKa4a8.<u></u>9a165b4901cf1602b3146c7f0bf0a1<u></u>91.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 69<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<br>
<br>
10:46:27.383907 IP 192.168.20.198.5080 > 192.168.20.214.5060<br>
SIP/2.0 100 Trying<br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bKa4a8.<u></u>9a165b4901cf1602b3146c7f0bf0a1<u></u>91.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
Record-Route: <sip:192.168.20.214;lr=on><br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
User-Agent: IMX<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.553363 IP 192.168.20.198.5080 > 192.168.20.214.5060<span class=""><br>
SIP/2.0 407 Proxy Authentication Required<br></span>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bKa4a8.<u></u>9a165b4901cf1602b3146c7f0bf0a1<u></u>91.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=Ke2rvve07SK3N<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
User-Agent: IMX<br>
Accept: application/sdp<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Proxy-Authenticate: Digest realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", algorithm=MD5, qop="auth"<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.553574 IP 192.168.20.214.5060 > 192.168.20.198.5080<br>
ACK sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bKa4a8.<u></u>9a165b4901cf1602b3146c7f0bf0a1<u></u>91.0<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=Ke2rvve07SK3N<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 ACK<br>
Max-Forwards: 69<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.553718 IP 192.168.20.214.5060 > 192.168.20.215.5062<span class=""><br>
SIP/2.0 407 Proxy Authentication Required<br></span>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=Ke2rvve07SK3N<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 INVITE<br>
User-Agent: IMX<br>
Accept: application/sdp<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Proxy-Authenticate: Digest realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", algorithm=MD5, qop="auth"<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.592662 IP 192.168.20.215.5062 > 192.168.20.214.5060<br>
ACK sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK1598556947<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=Ke2rvve07SK3N<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 1 ACK<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.630142 IP 192.168.20.215.5062 > 192.168.20.214.5060<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Proxy-Authorization: Digest username="1001", realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", uri="sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.<u></u>etellicom.com</a>", response="xxx", algorithm=MD5, cnonce="xxx", qop=auth, nc=00000001<br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 70<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<br>
<br>
10:46:27.630721 IP 192.168.20.214.5060 > 192.168.20.215.5062<br>
SIP/2.0 100 trying -- your call is important to us<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
Server: kamailio (4.1.5 (x86_64/linux))<br>
Content-Length: 0<br>
<br>
<br>
10:46:27.630896 IP 192.168.20.214.5060 > 192.168.20.198.5080<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Record-Route: <sip:192.168.20.214;lr=on><br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bK74a8.<u></u>d3d3ad8bb9b1c73c12e16cdab44747<u></u>2e.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Proxy-Authorization: Digest username="1001", realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", uri="sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.<u></u>etellicom.com</a>", response="xxx", algorithm=MD5, cnonce="xxx", qop=auth, nc=00000001<br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 69<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<br>
<br>
10:46:27.631731 IP 192.168.20.198.5080 > 192.168.20.214.5060<br>
SIP/2.0 100 Trying<br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bK74a8.<u></u>d3d3ad8bb9b1c73c12e16cdab44747<u></u>2e.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
Record-Route: <sip:192.168.20.214;lr=on><br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
User-Agent: IMX<br>
Content-Length: 0<br>
<br>
<br>
10:46:29.187901 IP 192.168.20.198.5080 > 192.168.20.214.5060<br>
SIP/2.0 302 Moved Temporarily<br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bK74a8.<u></u>d3d3ad8bb9b1c73c12e16cdab44747<u></u>2e.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
Max-Forwards: 69<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=mQUHyQZ3429NH<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
Contact: "unknown" <sip:<a href="http://node1.etellicom.com" target="_blank">node1.etellicom.com</a>><br>
User-Agent: IMX<br>
Accept: application/sdp<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Reason: Q.850;cause=31;text="NORMAL_<u></u>UNSPECIFIED"<br>
Content-Length: 0<br>
X-imx-redirect: sip:<a href="http://192.168.20.214:5080" target="_blank">192.168.20.214:5080</a><br>
<br>
<br>
10:46:29.188327 IP 192.168.20.214.5060 > 192.168.20.198.5080<br>
ACK sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bK74a8.<u></u>d3d3ad8bb9b1c73c12e16cdab44747<u></u>2e.0<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=mQUHyQZ3429NH<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 ACK<br>
Max-Forwards: 69<br>
Content-Length: 0<br>
<br>
<br>
 7(17488) ERROR: <script>: SCRIPT: REDIRECT, Store avp for redirect: sip:<a href="http://192.168.20.214:5080" target="_blank">192.168.20.214:5080</a><br>
 7(17488) ERROR: <script>: SCRIPT: REDIRECT: going to <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>> via <sip:<a href="http://192.168.20.214:5080" target="_blank">192.168.20.214:5080</a>><br>
<br>
10:46:29.432573 IP 192.168.20.214.5060 > 192.168.20.215.5062<span class=""><br>
SIP/2.0 407 Proxy Authentication Required<br></span>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=ZS5Q6Xem0Umaj<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 INVITE<br>
User-Agent: IMX<br>
Accept: application/sdp<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, path, replaces<br>
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Proxy-Authenticate: Digest realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="eac7076b-4c13-4492-<u></u>838c-14039cc2beb6", stale=true, algorithm=MD5, qop="auth"<br>
Content-Length: 0<br>
<br>
<br>
10:46:29.452446 IP 192.168.20.215.5062 > 192.168.20.214.5060<br>
ACK sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK416062902<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>>;tag=ZS5Q6Xem0Umaj<br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 2 ACK<br>
Content-Length: 0<br>
<br>
<br>
10:46:29.490390 IP 192.168.20.215.5062 > 192.168.20.214.5060<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK2079130033<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 3 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Proxy-Authorization: Digest username="1001", realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", uri="sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.<u></u>etellicom.com</a>", response="xxx", algorithm=MD5, cnonce="xxx", qop=auth, nc=00000001<br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 70<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<br>
<br>
10:46:29.490694 IP 192.168.20.214.5060 > 192.168.20.215.5062<br>
SIP/2.0 100 trying -- your call is important to us<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK2079130033<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 3 INVITE<br>
Server: kamailio (4.1.5 (x86_64/linux))<br>
Content-Length: 0<br>
<br>
<br>
10:46:29.490782 IP 192.168.20.214.5060 > 192.168.20.198.5080<br>
INVITE sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.com</a> SIP/2.0<br>
Record-Route: <sip:192.168.20.214;lr=on><br>
Via: SIP/2.0/UDP 192.168.20.214;branch=<u></u>z9hG4bK84a8.<u></u>289b7cd802ed6efd2f25721d6b8f29<u></u>d6.0<br>
Via: SIP/2.0/UDP 192.168.20.215:5062;branch=<u></u>z9hG4bK2079130033<br>
From: "1001" <<a href="mailto:sip%3A1001@test.etellicom.com" target="_blank">sip:1001@test.etellicom.com</a>>;<u></u>tag=1860002040<br>
To: <sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.etellicom.<u></u>com</a>><br>
Call-ID: <a href="mailto:1766438446@192.168.20.215" target="_blank">1766438446@192.168.20.215</a><br>
CSeq: 3 INVITE<br>
Contact: <<a href="http://sip:1001@192.168.20.215:5062" target="_blank">sip:1001@192.168.20.215:5062</a>><br>
Proxy-Authorization: Digest username="1001", realm="<a href="http://test.etellicom.com" target="_blank">test.etellicom.com</a>", nonce="xxx", uri="sip:*<a href="mailto:591000@test.etellicom.com" target="_blank">591000@test.<u></u>etellicom.com</a>", response="xxx", algorithm=MD5, cnonce="xxx", qop=auth, nc=00000001<br>
Content-Type: application/sdp<br>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE<br>
Max-Forwards: 69<br>
User-Agent: Yealink SIP-T38G 38.70.0.115<br>
Supported: replaces<br>
Allow-Events: talk,hold,conference,refer,<u></u>check-sync<br>
Content-Length: 310<br>
<br>
SDP<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a><br>
</div></div></blockquote></div><br></div>