One-X Mobile Partially connected. VOIP registration failed. 1

[Binkoba]

Hi

Server Edition, 10.1 (Virtual)

I am the Network Engineer (and IP Office engineer). The Mobile client says VOIP registration failed.

Looking at the Firewall packet sniffing I do not see and 5060 (SIP) attempts.

It says Error 16:0.

Lan1 SIP registration Enable check, SIP remote extension Check

YES, I have read the Manuals, YES, I have followed the manuals...

 

[AACon]

The user you are trying to register has the one-x mobile enabled on their user, yeah?
Do you have your FQDN populated in the domain name section in VOIP under lan 1? This should be the same fqdn you have as the server in your phone. Does the fqdn resolve to the WAN ip on your pbx?
Do you have that IP populated in the public ip address in your network topology? have you run stun?


-Austin
I used to be an ACE. Now I'm just an Arse.

 

[derfloh]

And please use an encrypted connection.

 

[TheSmash]

Using a browser, post what you see using the below;
https://[IPADDRESS]:8444/rest/my/im-info
https://[IPADDRESS]:8444/rest/my/sip-info


ACSS (SME)

 

[Binkoba]

To both of these I get a Login window
https://[IPADDRESS]:8444/rest/my/im-info
https://[IPADDRESS]:8444/rest/my/sip-info


It says

Authentication Required

 

[Binkoba]

User registered, Yes
Fqdn populated, Yes ipo.shbi.com
Resolves and the One -X mobile connects and gives updates etc, just no SIP traffic.
Network address populated, YES

 

[tlpeter]

did you enter a stun server on the ipo on the right lan port?
Firewall settings on that port in the ipo perhaps?
IP route with 0.0.0.0?


BAZINGA!

I'm not insane, my mother had me tested!

 

[Binkoba]

Thanks for the assistance,

IP route is fine, IPO has internet access, as Onex portal works.

Firewall has been tested wide open, still, not SIP connection attempt from Mobile device.

But, I will add that I am trying to get a B179 SIP conference phone to register, and it will not register either, and it is on the same LAN segment as the IPO.

 

[derfloh]

Do you have "Remote Extension" enabled on the LAN interface?

 

[Binkoba]

Sure Do

For internal SIP extensions, does SIP Domain Name and SIP registrar FQDN need any entries, Documentation seems to say they do not?

 

[Binkoba]

Here is the SIP Phone, IP Office account and IP Office SIP configuration details,

IP Office monitor says

11:01:41 2257740mS SIP Reg/Opt Tx: phone
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.17.89.155:5060;rport;branch=z9hG4bKPjmNeWUST8r9uBDPIBHvcq7cFkKDJDlO5y;alias
From: <sip:30001@10.17.90.220>;tag=opyChcvMQxJxbDfEfqnv0JgZqilz3Qfm
Call-ID: RsP81PcbKBcmiD-JlLS4OOZ1r1YqdOF3
CSeq: 14682 REGISTER
User-Agent: IP Office 10.1.0.0.0 build 237
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,INFO,SUBSCRIBE,REGISTER,PUBLISH

http://WWW-Authenticate:

Digest nonce="88d41a364800fe39ccf7",realm="ipoffice",algorithm=MD5
Supported: timer
Server: IP Office 10.1.0.0.0 build 237
To: <sip:30001@10.17.90.220>;tag=4981ad584e009af0
Content-Length: 0

 

[Pepp77]

Password on the B179 is not the password on the user tab, but the login code on the Telephony-Supervisor tab.

For the one-x mobile you need the correct settings on SIP Domain name (shbi.com) and SIP register FQDN (ipo.shbi.com), this one is the same as used on the one-x portal setup. Then you need the FQDN to be resolvable to the correct IP address (public and private) - which it should be already if the one-x server is reachable via the FQDN.

Also change the remote ports to something else other than 5060 (6743 is better, purely because it is more random and not the default)

It is also good practice to enable the keepalive option on the VoIP tab.

Finally have you entered the public IP that the FQDN resolves to on the network topology tab?

| ACSS SME |

 

[Binkoba]

On the B179 SIP issue, I still get the same error after setting the login code to match on both.

The internal hostname (Active Directory DNS entry too) shbi-90-avaya.shbi.com and the FQDN DNS name ipo.shbi.com are different, could that cause any issues down the road?

Network topology needs some work, as we have two ISPs, the FQDN is pointed to one of them (Comcast), and the outgoing traffic sources from the other ISP, I can see maybe that will cause a problem.

 

[nitinbh]

Can you set the SIP Domain Name and FQDN in the Voip settings and check if it helps?