Issue with One-X Mobile preferred for IP Office

[HBPSYS]

Hi I have ONE X Portal Installed as an application server and my voicemail pro server on Windows 2008 r2. Phone System is running 8.1. One-X Portal works fine internally and externally and I have also installed the ONE-X Mobile preferred application on my mobile. I can make calls using this app no problem and the phone system rings me back. All the IM stuff works as well and can also use the conference facilities. The issue is when I make a call or receive a call I have no options for transfer or hold all I get is the standard IPhone active call screen. I have read the documentation and don't believe I have missed nay steps. Its almost like I need to configure all the FNE codes but I believed this was just for ONE X Mobile essential edition. Also on top of this if I try to play the voicemails through the app its just says "error".

Any help is much appreciated

Thanks

HBPSYS

 

[tlpeter]

You will need to enable the mobile call control and use ** (within a second) and then dial the number you want.
When you upgrade to 9.0 then there will be an option to transfer calls but this is a big upgrade so make sure you know it all and what costs it will have.


BAZINGA!

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

 

[HBPSYS]

Hi tlpeter thanks for the reply that makes sense there must a been a mixup with 8.1 and 9 documentation. I have the upgrade licences for 9 so will be upgrading soon. Do the transfer options only work if its a SIP call and not a mobility/twinning call oo version 9? Also the ** doesn't seem to do anything on my phone for some reason. Customer just here's the button press but doesn't get put on hold

Cheers

 

[TelecomsTim]

I can't get mine working remotely without a VPN.

I have read the knowledgebase multiple times and checked my firewall rules about another 20 times but still app says it still can't connect to server.

 

[HBPSYS]

To be honest im in the same boat tried running traces on the firewall etc I can't understand why it doesn't work, May be a daft question but I assume all the voip port forwards on the firewall should point to the Phone system IP and not the one-X server and all one-X ports to the one-x portal server, as in the one-xmobile client there are no options for voip just the DNS name which in my case is my windows one-portal server. If this is the case a single external ip/DNS record would have to be used for both the One-xportal server and the phone system.

Any advice appreciated

 

[jamie77]

We have this as 1 public IP and 2 DNS records and works like a charm.

5060 and RTP ports point to phone system, all others point to OXP server. You also need to use STUN on the LAN port they connect to.

FQDN used needs to be put into presence setting on OXP and 2nd FQDN needs to be put into IPO. Remote Worker and stuff then needs to be turned on.

If you make the DNS record used outside the office work from your internal WiFi you can test the basic setup without involving the firewall to make sure the IPO and OXP are setup ok first.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[HBPSYS]

Thanks Jamie great info will give another try . Did get the VoIP to work internally but didn't put a fqdn on the ip office for the VoIP so will try this and use 2 DNS entries for internal and external access to the 1 IP.

Thanks

 

[tlpeter]

For who can't get it working.

1 Do you have 2 FQDN?
2 Do you use split DNS?
3 Which ports do you have forwarded and to where?
4 Does the IPO has SIP remote worker configured?
5 Does the One-X Portal server has an FQDN configured?
6 Does the user has mobility VOIP enabled and does it have a user password configured?


BAZINGA!

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

 

[teletomi]

@tlpeter atr your questions for voip client for version 9..?

 

[jamie77]

Yes they are. Buddy notice the 8.1 bit. Loads of people asking the same things about the new caliber. My bad.

The 8.1 needs all the sand apart from the IPO forwarding stuff.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[teletomi]

@jamie77 thanks for the reply. i'm confused with the split DNS thing. I thought i can do this to ver 8.1. because the client is now asking me to use their public ip address in connecting to their one x mobile app. but they're only at ver 8.1 and need to upgrade. so i will tell to the client that split dns only happens at ver 9.0 right?

 

[tlpeter]

Sorry, 8.1 does not need the split DNS.
You will need one FQDN pointing to the One-X Portal server and put the FQDN in there.
If you are going to upgrade then do not put it on the public internet but use a router or firewall for this and a DNS server.



BAZINGA!

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

 

[jamie77]

Just read my last post back. Must stop replying late at night from my iphone. Everything stops making sense!!

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[HBPSYS]

Hi Everyone thanks for all you posts and help on this in the end I have now got this to work he is how I have it configured.

[ul]
[li][/li]
[/ul]Setup two External and internal DNS entries of onexportal.abc.com and onexmobile.abc.com and pointed the external ones to my single external IP address and the internal ones to the One-X Portal server and the other to the IP of the Avaya Office LAN1 IP
[ul]
[li][/li] Then on the firewall in my case a Watchguard I added to following Nat Rules One rule Called One-X Portal and redirected ports TCP 5222,8444,5269,8080,8063,8443 and 9443 and pointed these to the One-X Portal Server internal IP. I then added the DNS name of Onexportal.abc.com to the IM Presence XMPP Domain name in the one X Portal configuration settings
[/ul]
[ul]
[li][/li] Then added a second NAT rule for SIP/H323 traffic and redirected ports 5060 TCP/UDP, 5061 TCP/UDP ,1719-1720 and 49152-53246. This was also for the remote 9600 phones to be able connect.
[/ul]
[ul]
[li][/li]Then the only other thing I did was on the Avaya IP office Lan1 Voip TAB and entered in onexmobile.abc.com into the Domain Name turn on the SIP and H323 Gatekeeper etc and under Network Topology Tab and set the firewall/Nat Type to Static Port block ,entered my public IP address (The one that the external DNS entries pointed to)and rebooted the phone system.
[/ul]

After this Voip then worked externally. On My 2 firewall Rules granted there seems to more ports in there then I think I needed especially the rule for ONE-X Portal but at the moment its all working so reluctant to take any out. The only thing that doesn't work for me is I can't seem to play the voicemails on the APP it just doesn't do anything but all else seems good for now.

Any feedback appreciated

Cheers

 

[tlpeter]

Are you a hotdesk user?
This was a bug and i must say i thought it was fixed but it seems to be back.

BAZINGA!

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

 

[HBPSYS]

Ha thanks Tlpeter that explains it then I am a hot desk user will try and turn it off and test it

Thanks

 

[TelecomsTim]

Going to spend some more time on this when I am back in the office later this week.

One question I have is the FQDN necessary or can you just point to the public IP address of the firewall?

I think this is where I may be falling down but IT reckon the FQDN shouldn't be required. I admit my knowledge on FQDN's and split DNS is somewhat limited!

 

[tlpeter]

Android can handle an IP address but iPhone's seem to have problems with that but last time i tried it did work.



BAZINGA!

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

 

[HBPSYS]

I think for the one x clients it makes sense to use the fqdn and point it to you external ip, but why do you need a second one for the sip as mine just points to the same IP and my VoIP connection on the client worked ok internally before I entered the domain name in the VoIP tab on lan1 so I don't get how that works?

 

[TelecomsTim]

Thanks!

I also don't have STUN turned on on the LAN port of the IPO so this maybe causing the issue.