<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Klaus,<br><br>Thanks. I removed to tag check from config file.<br><br>Thanks<br>Sid<br><br><div><span style="font-weight: bold; color: rgb(45, 45, 45);"><font color="#0000ff" size="4">"May the light be with you."</font></span></div> <div><span style="font-weight: bold; color: rgb(45, 45, 45);"></span><span style="font-family: arial;">______________________________________________</span><br style="font-family: arial;"><font style="font-family: arial;" size="4"><font style="font-family: arial;" size="3"><font color="#407f00"><span style="font-weight: bold;">Siddhardha Garige</span><br style="font-weight: bold;"></font><a rel="nofollow" style="font-weight: bold;" target="_blank" href="http://www.luminepixels.com/"><font color="#407f00">www.luminepixels.com</font></a></font><br style="font-weight: bold;"></font><br></div><br><br>--- On <b>Mon, 9/6/10, Klaus
Darilion <i><klaus.mailinglists@pernau.at></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Klaus Darilion <klaus.mailinglists@pernau.at><br>Subject: Re: [SR-Users] Routing issues with SIP Route headers.<br>To: "Siddhardha Garige" <siddu999@yahoo.com><br>Cc: "SR-Users" <sr-users@lists.sip-router.org><br>Date: Monday, September 6, 2010, 4:34 AM<br><br><div class="plainMail">The REGISTER request contains the "pre-loaded route set". Pre-loaded <br>route sets are for security reasons disabled in the default config <br>(to-tag check):<br><br>if (has_totag()) {<br> # sequential request withing a dialog should<br> # take the path determined by record-routing<br> if (loose_route()) {<br> ...<br> route(RELAY);<br> } else {<br>
...<br><br>Either remove the totag check or add an explicit entry (eg. before the <br>above block):<br><br>if (is_method("REGISTER") {<br> # allow pre-loaded route set for REGISTER<br> if (loose_route()) {<br> ...<br> route(RELAY);<br> }<br>}<br><br><br>regards<br>Klaus<br><br><br>Am 02.09.2010 17:05, schrieb Siddhardha Garige:<br>> Hello all,<br>><br>> I am having little trouble routing registrations based on route header<br>> in following configuration. UA sends registration to P1 and P1 is<br>> ignoring “route header” and forwards registration request to Registrar.<br>><br>> I am using default kamailio configuration. Is there any thing I need to<br>> add to default config to enable route headers?<br>><br>><br>>
UA----------------->proxy1(kamailio)------------------->proxy2------------------>Registrar<br>><br>> REGISTER sip:Registrar.com SIP/2.0<br>><br>> Via: SIP/2.0/UDP 10.18.0.67:5060;branch=z9hG4bKd209323e;rport<br>><br>> Route: <sip:proxy2.com;lr><br>><br>> Max-Forwards: 70<br>><br>> From: <sip:<a ymailto="mailto:xxxxxx@registrar.com" href="/mc/compose?to=xxxxxx@registrar.com">xxxxxx@registrar.com</a>>;tag=a85f9424<br>><br>> To: <sip:<a ymailto="mailto:xxxxx@registrar.com" href="/mc/compose?to=xxxxx@registrar.com">xxxxx@registrar.com</a>><br>><br>> Contact: <sip:xxxxxxx@10.18.0.67><br>><br>> Call-ID: 431368ae25a3e232<br>><br>> CSeq: 100 REGISTER<br>><br>> Expires: 840<br>><br>> Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,UPDATE,SUBSCRIBE,NOTIFY<br>><br>> Supported:<br>><br>> User-Agent: xg-tx60 3.1.17 (VeriCall Edge)<br>><br>> Content-Length:
0<br>><br>><br>> Thanks<br>><br>> Sid<br>><br>><br>><br>> "May the light be with you."<br>> ______________________________________________<br>> Siddhardha Garige<br>> www.luminepixels.com <<a href="http://www.luminepixels.com/" target="_blank">http://www.luminepixels.com/</a>><br>><br>><br>><br>><br>> _______________________________________________<br>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>> <a ymailto="mailto:sr-users@lists.sip-router.org" href="/mc/compose?to=sr-users@lists.sip-router.org">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></div></blockquote></td></tr></table><br>