Avaya One-X Mobile fully connected disabled when VOIP

[PeterG911]

Hello ...

Finally, I have one-x mobile fully connected, but when I moved to VOIP down to partially connected. this case when I used it as SIP.
in monitor, sip phone status (disable, no license).
this user I create it manually .
when I connected it as a desktop user its fully connected, but when I use it, dialing from deskphone and I cant control it already no voice, just as a remotely control my phone in incoming and outgoing call.

all the configuration per-requisites is done. this test is on the customer WiFi, customer will use VPN from outside.


Thank you on your Help and Advance.

 

[sizbut]

Okay, the words are English but they make little to no sense.

Stuck in a never ending cycle of file copying.

 

[Pepp77]

All the configuration pre requisites are done.

No they are not otherwise it would be working

| ACSS SME |

 

[PeterG911]

Hello ...

Some help please and confirm if I have done this correctly...
I have two FQDN's one for IP office (ipo.xxx.com) resolving to the Lan1 address and one for the application server (ucserver.xxx.com) resolving to application server IP address. Both those IP's and NAT'ed to the 1 public IP 41.x.x.x

I have added the IP office FQDN (ipo.xxx.com) to the Lan 1 Voip tab domain name field and the UCserver FQDN to the application server
XMPP address field.

My one x on GSm (3g) works fine with call back but my VOIP fails to register.

What am I doing wrong?
Should the 2 FQDN's point to one Ip address internally?

Any feedback appreciated

 

[PeterG911]

Hi ...

I have again facing a problems with the IT in new IPO implementation, the customer have 20 power user ans need to deploy it as a one-x mobile on voip mode as a sip phone to using calling faciltiy. as you you know monitor mode not acceptable to him. describe to him the process and send to him how this works with avaya and this is need a working from him on dns and firewall. see whats he repaly to me:
"I need the One-X mobile to be run internal the network not from the external, please sign a ticket with Avaya to solve this."

please ya avaya how one-x work internally with the customr, note that the one-x alreddy connnectec locally but this not satisfied to him becuase the application on monitor mode cant give him a call facility as he need.

please I need you a proffesionl replay to tell the customer its impossible the one-x voip mode works internally.

Thanks

 

[PeterG911]

Please Read carefully this email and first the attached , I will describe on it the Avaya one-x mobile application, step by step configuration.

Implementing Avaya's One-X portal is pretty painless, until you want to deploy this to the Android and iPhone clients when these clients are outside of your network. The clients will also work within your local network. Here is our experience and solution. Your mileage may vary depending on the resources available to you.
1. Notice that we are using a "Split DNS" configuration which simply means that we have DNS records for KADDB.com on our internal DNS server(s) as well as external DNS server(s). The Internal DNS Server has the records that point the Fully Qualified Domain Name (FQDN) of each server to the internal IP addresses and the External does the same with the external IP addresses. It is important that these names and addresses be established before doing any configuration of the IPO or the One-X Server.
in our enviroment the following DNS records were created;
Internal DNS Server 'A' Records
avaya.KADDB.com =172.16.0.131 (one-x portal Server)
ipo.KADDB.com = 172.26.0.254 ( ipo LAN1 )
2. Now we need to point those FQDN's to an external IP address of the router/firewall and this is port forwarded to the IPO.
Both FQDN's also need to be entered in the DNS server for using it internally.
Public IP :
x.x.x.x = avaya.KADDB.com
internal IP:
172.16.0.131 = avaya.KADDB.com
On the Mobile application under server ID we will use avaya.kaddb.com.
Public IP x.x.x.x NAT to 172.16.0.131
both of those DNS entries should resolve to a public IP. The public IP should NAT to your internal One XPortal Server IP local IP
3. Configure your NAT Firewall:



IP Office: 172.26.0.254
Avaya one-X portal Server: 172.16.0.131

Note: Ensure that you turn on NO SIP-ALG.

Once our DNS records are all created properly and our NAT firewall port forwards are completed, we can use this information to get our One-X and IPO configurations completed.
Now, as long as you have all of the proper licensing, your should see the Avaya One-X Mobile Application show fully connected and ready to go!

 

[janni78]

If your custoemr says they only wan't to use it on internal network you don't need to bother with external IPs and NAT.

"Trying is the first step to failure..." - Homer

 

[PeterG911]

Hi ...

ok, how this can work internally with voip mode ?


Thanks

 

[DaIPOTek]

Sounds like you need re re-read the documentation. You should be able to close your eyes and make it work internally

 

[holdmusic34]

If you're not connecting from externally, just put the IP Address of your Onex Server in the FQDN settings.

Put the ip address in Onex Mobile Client, turn security settings off and it should work.

Gunpoint 132 and Bush.Cover's code three

 

[PeterG911]

@holdmusic34: I dont have the option H.323 Signalling over TLS. already I set VOIP Security to Disabled. (LAN1>VOIP)
Just I have SIP Domain Name, I dont have box for SIP Register FQDN.

it should be change the XMPP in the One-X Server from avaya.Kaddb.com to IP Adress of the server.

Thanks

 

[PeterG911]

@DaIPOTek: I read all the Avaya Technical Document (Knowledge Base), I have Avaya Learning Training document, I read all the discussion here in tek-tips and Avaya.support fourm, I read all the discussion on the web about one-x mobile.
not found any talking about run one-x mobile on the voip mode locally.
already I tell working internally just in the monitor mode but when move to voip down to partially connected.
anyway thanks you all, we are on this fourm to discuss and help each other of our experience.
thank you @@holdmusic34.

Thanks

 

[janni78]

Let's look at it this way...

Why do you think they say you need Split DNS ?

Because you want the same functionality when you're on the office WiFi as when you out of office, as in VoIP mode should work locally as well as from external destination.
If you only want local access you cut of the external part and getting it to work locally should be the easy part.

"Trying is the first step to failure..." - Homer

 

[PeterG911]

Thank you all for the help.

 

[DaniWG]

@holdmusic34: I think this way you suggested is only new for Rls10, PeterG911 talking about Rls9.1 SP10. I think he should working on the local DNS to pointing to the internal IP addresses of the IP500 and One X Portal server.

 

[derfloh]

In R9.1 the SIP domain is used as SIP FQDN as well.