Cannot be authenticated

Russell · Post by **Russell** » Wed Jul 22, 2015 7:08 pm

1. Brekeke Product Name and Version: SIP Server (3.4.6.3/411)

2. Java version: 1.7

3. OS type and the version: Linux

4. UA (phone), gateway or other hardware/software involved:

X-Lite, Zoiper (iOS SIP Phone), ABTO (iOS SIP Phone)

5. Your problem:

I just install the sip.war on tomcat 7 and created 3~4 AU accounts. I left the rest of the setting by default. All 3 SIP client phones were unable to register as users.

PS. 1. the firewall has the 5060 port (both UDP and TCP) open to public.

2. The dial plan has register records:

No. Session ID Method Request URI Rule Source IP Destination IP Response Code Time
416 REGISTER sip:x.x.x.x register x.x.x.x:7354 (TCP) 02:39:05.945
417 REGISTER sip:x.x.x.x register x.x.x.x:35482 (UDP) 02:39:10.028
418 REGISTER sip:x.x.x.x register x.x.x.x:44441 (UDP) 02:39:39.115
419 REGISTER sip:x.x.x.x register x.x.x.x:56894 (TCP) 02:40:07.188
420 REGISTER sip:x.x.x.x register x.x.x.x:44441 (UDP) 02:40:33.080
421 REGISTER sip:x.x.x.x register y.y.y.y:30051 (TCP) 02:41:05.753
422 REGISTER sip:x.x.x.x register x.x.x.x:44441 (UDP) 02:41:26.142
423 REGISTER sip:x.x.x.x register x.x.x.x:1666 (TCP) 02:42:08.220
424 REGISTER sip:x.x.x.x register y.y.y.y:4200 (TCP) 02:43:07.204
425 REGISTER sip:x.x.x.x register x.x.x.x:39094 (UDP) 02:43:15.321

Mike · Post by **Mike** » Wed Jul 22, 2015 9:56 pm

Check the SIP Server's interface IP address in the [Status] page.

Is it the IP address what you set as the SIP proxy in SIP client's setting?

Russell · Post by **Russell** » Wed Jul 22, 2015 10:07 pm

Hi:

No, it's the private IP address (similar to 192.168.x.x) instead of the public address.

I fixed the problem by adding a new interface address in "Configure" page.

Thanks for your help.

Russell

ambrosio · Post by **ambrosio** » Thu Jul 23, 2015 9:47 am

Which Linux distribution are you using?
Brekeke SIP Server picks OS's interface IP addresses automatically so you don't have to set it manually in most cases.

Are you using a router's port-forwarding to forward SIP packets to the Brekeke SIP Server?

Russell · Post by **Russell** » Thu Jul 23, 2015 6:11 pm

Hi,

Yes, it's behind a firewall. So there is no way that the server itself would know its own public IP.

It's AWS-Linux. I didn't know that the sip server has to know its public IP before it would authorize users.

Thanks,

ambrosio · Post by **ambrosio** » Thu Jul 23, 2015 10:45 pm

Have you read this? http://wiki.brekeke.com/wiki/Set-port-forwarding

If your router supports UPnP, the SIP server can pick a public IP automatically.

> I didn't know that the sip server has to know its public IP before it would authorize users

Because SIP packet's request-URI will indicate a public IP address if it is sent from Internet.

Russell · Post by **Russell** » Thu Jul 23, 2015 11:21 pm

Hi,

Thanks.

I believe the linux we are currently using doesn't have UPnP. Hence, I have to configure the extra network interface like you suggest in that document.

ambrosio · Post by **ambrosio** » Fri Jul 24, 2015 9:11 am

Brekeke SIP Server has own UPnP control-point feature, so Linux doesn't have to support it.

Cannot be authenticated

Cannot be authenticated

The server IP Address