[Spce-user] loose-routing

[Henk]

Hi Stefano,

I had to add the DNS name of my server to SPCE as a dummy domain to stop 
the loose-routing error. But if I look at your log, it seems you are 
using _voceblu.it_ and not geva.voceblu.it.
<http://geva.voceblu.it>Are both domains existing in SPCE?


In the script (/etc/kamailio/proxy/proxy.cfg) there is a test to see if 
the destination uri domain is local, if this fails it produces the 
loose-route error:

         if(!has_totag())
         {
             if($du != $null && _*is_domain_local("$dd")*_)
             {
                 xlog("L_INFO", "Reset initial local route - R=$ru 
ID=$ci UA='$ua'\n");
                 $du = $null;
             }
             else
             {
                 xlog("L_NOTICE", "_*Initial loose-routing rejected*_ - 
R=$ru ID=$ci UA='$ua'\n");
                 sl_send_reply("403", "Initial Loose-Routing Forbidden");
                 exit;
             }
         }

Hope this helps,

Regards,

Henk Plessius

On 5-11-2017 19:31, stefanormc wrote:
> Hi Henk,
>
> I’m no too sure what you mean. What proxy domain do you refer to?
>
> In my case, user is XXXXX at geva.voceblu.it 
> <mailto:XXXXX at geva.voceblu.it> and I have geva.voceblu.it 
> <http://geva.voceblu.it> realm configured
>
> Proxy is centrale.aXXXXXXti.it <http://centrale.aXXXXXXti.it> that 
> seems to be correctly configured on the Grandstream ATA
>
> Thanks
>
> ciao
>
> Stefano
>
> On 4 November 2017 at 21:04:09, Henk (henk at voipdigit.nl 
> <mailto:henk at voipdigit.nl>) wrote:
>
>> Hi Stefano,
>>
>> I had the same problem when I made a connection to an authorization 
>> domain which was not the same as the server address. In some clients 
>> you have to use the proxy setting to specify the server address. The 
>> kamailio proxy checks the domain against the known domains (domain 
>> table in the kamailio db). I solved this by adding the proxy domain 
>> in SPCE. Hope this helps for you too.
>>
>> Regards,
>>
>> Henk Plessius
>>
>>
>> On 4-11-2017 17:13, stefanormc wrote:
>>> Hello again,
>>>
>>> Anyone…? No ideas?
>>>
>>> I’m stuck
>>>
>>> Thanks
>>>
>>> Ciao
>>>
>>> Stefano
>>>
>>>
>>>
>>> On 3 October 2017 at 14:00:16, stefanormc (stefanormc at gmail.com 
>>> <mailto:stefanormc at gmail.com>) wrote:
>>>
>>>>
>>>> Hi all,
>>>>
>>>> I just updated to 5.4.1 and I’m experiencing a ‘loose routing’ 
>>>> problem on outbound calls from certain clients that are correctly 
>>>> registered and have no problem on inbound calls.
>>>>
>>>> This what I see in spce log:
>>>>
>>>> Oct  3 10:55:40 centrale proxy[3476]: NOTICE: <script>: New request 
>>>> on proxy - M=INVITE R=sip:0110133301 at voceblu.it 
>>>> <mailto:sip%3A0110133301 at voceblu.it>;user=phone 
>>>> F=sip:0119649202 at voceblu.it 
>>>> <mailto:sip%3A0119649202 at voceblu.it>;user=phone 
>>>> T=sip:0110133301 at voceblu.it 
>>>> <mailto:sip%3A0110133301 at voceblu.it>;user=phone IP=172.26.4.92:1024 
>>>> <http://172.26.4.92:1024> (127.0.0.1:5060 <http://127.0.0.1:5060>) 
>>>> ID=1052434700-5060-11 at BJC.BGI.B.H UA='Grandstream HT701 1.0.8.2'
>>>> Oct  3 10:55:40 centrale proxy[3476]: NOTICE: <script>: Initial 
>>>> loose-routing rejected - R=sip:0110133301 at voceblu.it 
>>>> <mailto:sip%3A0110133301 at voceblu.it>;user=phone 
>>>> ID=1052434700-5060-11 at BJC.BGI.B.H UA='Grandstream HT701 1.0.8.2’
>>>>
>>>> Outbound calls worked fine before upgrading
>>>>
>>>> Any hint where the problem might lie?
>>>>
>>>> Thanks
>>>>
>>>> stefano
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>> https://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/20171105/b21746f6/attachment-0001.html>