<div dir="ltr">i was thinking of changing the record-route before sending out.<div>I tried it, but it's not working</div><div><br></div><div><div> subst_hf("Record-route", "/^<sips:<a href="http://1.2.3.4:6055">1.2.3.4:6055</a>\(.*\)$/<sip:<a href="http://1.2.3.4:6055">1.2.3.4:6055</a>\1/", "a");</div></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">Kelvin Chua</div></div>
<br><div class="gmail_quote">On Wed, Mar 4, 2015 at 2:52 PM, Kelvin Chua <span dir="ltr"><<a href="mailto:kelchy@gmail.com" target="_blank">kelchy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">just an idea, will it work if i used subst_hf?</div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div>Kelvin Chua</div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Tue, Mar 3, 2015 at 5:16 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<div><br></div><div>We need to review this in rr.</div><div><br></div><div>Meanwhile you can use s.substr transformation to get whats after sips and prefix it with sip in r-uri.</div><div><br></div><div>Cheers,</div><div>Daniel<div><div><span></span><br><br>On Tuesday, March 3, 2015, Kelvin Chua <<a href="mailto:kelchy@gmail.com" target="_blank">kelchy@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Found the problem, on the 200 OK, I have this record route list</div><div><br></div><div><div>Record-Route: <sips:<K2 IP>:6056;transport=tls;r2=on;lr;ftag=as620b910c;did=242.fd92;nat=yes>.</div><div>Record-Route: <sips:<K2 IP>:6055;r2=on;lr;ftag=as620b910c;did=242.fd92;nat=yes>.</div><div>Record-Route: <sip:<K1 IP>:5080;lr=on;did=242.968></div></div><div><br></div><div>the second entry is wrong. it should be sip: and not sips:</div><div>how can we force this? protocol pv is read-only</div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div>Kelvin Chua</div></div>
<br><div class="gmail_quote">On Tue, Mar 3, 2015 at 2:43 PM, Daniel-Constantin Mierla <span dir="ltr"><<a>miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
doesn't the ACK have a Route header for K1 and double Route headers
for K2? K1 should use the first Route of K2 for routing, not the
R-URI.<br>
<br>
Cheers,<br>
Daniel<div><div><br>
<br>
<div>On 03/03/15 05:14, Kelvin Chua wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">
<div>I have 2 kamailio servers and 1 asterisk server.</div>
<div><br>
</div>
<div>1. asterisk calls kamailio1</div>
<div>2. kamailio1 relays INVITE to kamailio2</div>
<div>3. kamailio2 relays INVITE to client registered using TLS</div>
<div>4. client answers with 200 OK, sends to kamailio2</div>
<div>5. kamailio2 relays 200 OK to kamailio1</div>
<div>6. kamailio1 relays 200 OK to asterisk</div>
<div>7. asterisk sends ACK to kamailio1</div>
<div>8. kamailio1 complains "forward_request(): forward_req:
ERROR: cannot forward to af 2, proto 3 no corresponding
listening socket" which is because 200 OK has a contact header
with tls transport from client</div>
<div>9. call drops in 30 secs which is expected because client
never received the ACK</div>
<div><br>
</div>
<div>any ideas on a fix or workaround?</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>Kelvin Chua</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a>sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span><font color="#888888">
</font></span></pre><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - <a href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a></pre>
</font></span></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a>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/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><span><font color="#888888"><br><br>-- <br><div dir="ltr"><div>Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a></div><div><a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/micond</a></div></div><br>
</font></span></blockquote></div><br></div></div></div>
</blockquote></div><br></div>