[Spce-user] authentication with peerings

[Joan Cifre (ibred)]

Hello again
I've made some changes in my configuration. I had to restart the whole 
server with ngcpcfg apply, because only restarting sems does not apply 
the configuration of reg_agent.conf.tt2 file

Now I'm getting this

#
U 176.31.116.108:5060 -> 141.105.111.231:5060
SIP/2.0 403 Forbidden.
Via: SIP/2.0/UDP 141.105.111.231;branch=z9hG4bKa53.9abf2655.0;rport=5060.
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKtbpJvayK;rport=5080.
From: 
<sip:user_12345 at pbx.globatel.net>;tag=0FE2EE58-4F7477EA0006296F-FBDC7700.
To: <sip:user_12345 at pbx.globatel.net>;tag=6BXyUX06y3a9Q.
Call-ID: 201167B5-4F7477EA000629AD-FC5CF700.
CSeq: 51 REGISTER.
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-d8ae59f 2011-10-28 
01-10-27 +0200.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, 
REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE.
Supported: precondition, path, replaces.
Content-Length: 0.


Now the Ip address of the peering server 176.31.116.108 is correct, but 
in the domain it should be user_12345 at ib-red.com, not 
user_12345 at pbx.globatel.net, because if not I'm getting a forbidden
If I include Domain=ib-red.com I can't get the server, and if I include 
Domain=pbx.globatel.net I can't register getting a 403 Forbidden
Any ideas?
Thanks!
Joan


El 29/03/2012 16:35, Joan Cifre (ibred) escribió:
> Hello Andreas,
> then I have an error in th configuration in my system, because the 
> server I have to reach is not ib-red.com. I have to reach the server 
> 176.31.116.108 (pbx.globatel.com) but with realm "ib-red.com"
> I don't understand exactly what it means, but these are the 
> requeriments that send me the provider, so I have configured 
> domain=ib-red.com in reg_agent.conf.tt2. In Sip Peering configuration
> Server 176.31.116.108
> peer_auth_realm: ib-red.com
>
>
>
> El 29/03/2012 15:23, Andreas Granig escribió:
>> Hi,
>>
>> On 03/29/2012 10:12 AM, Joan Cifre (ibred) wrote:
>>> Here you have the debug output. I can see a "failed registration" but I
>>> don't see the reason. The user is "user_12345"
>> It says "DEBUG: Received reply: 408 Request Timeout", which means the
>> host at sip:ib-red.com:5060 is not reachable from your system, or at
>> least doesn't answer your REGISTER.
>>
>> To verify that, you can do (adapt eth0 to whatever interface you use for
>> the public IP):
>>
>>     ngrep -W byline -d eth0 port 5060
>>
>> and watch the SIP REGISTER go out to the peer. You can force a
>> re-register by executing "/etc/init.d/sems restart". If you don't get a
>> reply, check with your peering provider if they get the message, and if
>> so, why they don't answer to that.
>>
>> Andreas
>>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/listinfo/spce-user