[Spce-user] Peer outbound re-write rules
Clint Wiley
cwiley at nfis.com
Tue Feb 25 14:07:32 EST 2014
Hmm. According to vim, I only have 5675 lines in that file.
Clint
On Feb 25, 2014, at 2:00 PM, Lorenzo Mangani <lorenzo.mangani at gmail.com<mailto:lorenzo.mangani at gmail.com>> wrote:
Clint,
They're in /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2 around line 5838
Lorenzo Mangani
HOMER DEV TEAM
QXIP - Capture Engineering
On Tue, Feb 25, 2014 at 7:53 PM, Clint Wiley <cwiley at nfis.com<mailto:cwiley at nfis.com>> wrote:
Hi all,
I was curious if anyone had any ideas. I’ve got to resolve this.
Clint
On Feb 24, 2014, at 10:17 AM, cwiley <clint at newfrontierssolutions.com<mailto:clint at newfrontierssolutions.com>> wrote:
> Hi,
>
> This went dormant as another project took center stage. However, I now have to resolve this again! I’ve followed your example below but cannot find the following lines to remove:
>
>> if(pv_isset("$xavp(caller_real_prefs[0]=>peer_auth_realm)"))
>> {
>> xlog("L_NOTICE", "Setting R-URI '$rU@$xavp(caller_real_prefs[0]=>peer_auth_realm)' using peer auth realm of subscriber - [% logreq -%]\n");
>> $ru = "sip:" + $rU + "@" + $xavp(caller_real_prefs[0]=>peer_auth_realm);
>> }
>> else if(pv_isset("$xavp(callee_real_prefs[0]=>peer_auth_realm)"))
>> {
>> xlog("L_NOTICE", "Setting R-URI '$rU@$xavp(callee_peer_prefs[0]=>peer_auth_realm)' using peer auth realm of peer - [% logreq -%]\n");
>> $ru = "sip:" + $rU + "@" + $xavp(callee_peer_prefs[0]=>peer_auth_realm);
>> }
>
> Any ideas?
>
> Clint
>
> On Dec 5, 2013, at 4:20 PM, Andrew Pogrebennyk <apogrebennyk at sipwise.com<mailto:apogrebennyk at sipwise.com>> wrote:
>
>> Hi Clint,
>>
>> Clint Wiley wrote:
>>> Hi,
>>>
>>> Here is the proxy log:
>>
>> the rewrite rule is applied properly and the call leaves the server
>> without 333 prefix:
>>
>> Dec 5 13:16:23 sipproxy2 /usr/sbin/kamailio[1711]: INFO: <script>:
>> Relaying request, du='sip:sip.flowroute.com:5060<http://sip.flowroute.com:5060/>',
>> fs='udp:67.20.37.3:5060<http://67.20.37.3:5060/>' - R=sip:2405201302 at sip.flowroute.com<mailto:sip%3A2405201302 at sip.flowroute.com>
>> ID=NjdhOWM1MzFjYTRmMjgwMDkyNzY0N2EwYzU4OGZmOTY_b2b-1
>>
>> This 'sip:sip.flowroute.com:5060<http://sip.flowroute.com:5060/>' has caught my attention. From
>> proxy.log it looks like your peering IP address is 216.115.69.144.
>> However because of peer_auth_realm set to sip.flowroute.com<http://sip.flowroute.com/> proxy
>> changes R-URI to that address:
>>
>> Dec 5 13:16:23 sipproxy2 /usr/sbin/kamailio[1882]: INFO: <script>:
>> Setting R-URI using peer auth realm '2405201302 at sip.flowroute.com<mailto:2405201302 at sip.flowroute.com>' -
>> R=sip:2405201302 at 216.115.69.144<mailto:2405201302 at 216.115.69.144>:5060;transport=udp
>> ID=NjdhOWM1MzFjYTRmMjgwMDkyNzY0N2EwYzU4OGZmOTY
>>
>> Then it sends request to the lb which resolves sip.flowroute.com<http://sip.flowroute.com/> via DNS
>> SRV. The request goes somewhere, but probably not where you want it.
>>
>> Probably we should not overwrite R-URI with peer_auth_realm; we'll
>> review that. In the meantime you can disable this overwrite. Copy
>> /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.tt2 to
>> /etc/ngcp-config/templates/etc/kamailio/proxy/proxy.cfg.customtt.tt2 (if
>> it doesn't exist yet) and remove the following lines (for version 3.1,
>> in 2.8 search for the line which says "Setting R-URI using peer auth
>> realm"), save and ngcpcfg apply:
>>> if(pv_isset("$xavp(caller_real_prefs[0]=>peer_auth_realm)"))
>>> {
>>> xlog("L_NOTICE", "Setting R-URI '$rU@$xavp(caller_real_prefs[0]=>peer_auth_realm)' using peer auth realm of subscriber - [% logreq -%]\n");
>>> $ru = "sip:" + $rU + "@" + $xavp(caller_real_prefs[0]=>peer_auth_realm);
>>> }
>>> else if(pv_isset("$xavp(callee_real_prefs[0]=>peer_auth_realm)"))
>>> {
>>> xlog("L_NOTICE", "Setting R-URI '$rU@$xavp(callee_peer_prefs[0]=>peer_auth_realm)' using peer auth realm of peer - [% logreq -%]\n");
>>> $ru = "sip:" + $rU + "@" + $xavp(callee_peer_prefs[0]=>peer_auth_realm);
>>> }
>>
>> Regards,
>> Andrew
>
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
http://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140225/dffd7d10/attachment-0001.html>
More information about the Spce-user
mailing list