Avaya Support Forums  

Go Back   Avaya Support Forums > Small and Medium Business Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-03-2017, 12:46 PM
mqatatsheh mqatatsheh is offline
Brainiac
 
Join Date: Dec 2012
Posts: 67
mqatatsheh has 10 reputation points
Default AVAYA IPO One-X Mobile through VPN

Hi all..

Our customer is using IPO 500v2 R9.1.10 The customer wouldn't like to use a Avaya IPO One-X Mobile as a VOIP Mode. They would want to use their own VPN connection .. The customer is using their VPN. Port forwarding rule has not been done yet. Customer tell all the ports Opened locally.
First Attempt the mobile application is fully connected, a while its become partially connected. we can make a call from it through desk phone (all IPO contact now in the mobile phone), not ringing when receiving and when the caller hang up the calls appears in missed call.
I am testing Avaya One-X mobile with voip on the following scenario:
However voip is not working. When I turn on voip, the Icon on my mobile yellow with an error : The application is operational with the exception of the VoIP feature which is experiencing problems registering with the server. (error 16:0) / or ( error:13)
I have setup and follow Avaya Document and all threats on this fourm:
- VoIP feature will only be available on the application if:
- User license is ‘Power user’
- VoIP is enabled for the user in IPO Manager Done
- G.722 enabled and selected on IP Office in the Codec tab in the System form
- The client supports G.711a/mu, G.722 and G.729A
- Under Menu key->Settings->VoIP Operation Mode choose Wifi only when Mobile Fallback
- Port 5061 is TLS on the IPO option checked.
- I can connect to the one-x portal interface web interface on the computer with this login.
- This is my topology
172.26.0.254 is my ipo 500 box
172.16.0.131 is my one x portal server ( XMPP: AVAYA.KADDB.COM)
LAN >> VOIP : H.323 GateKkeeper Enabal (checked), H.323 Remote Ext Enable (Checked), Auto Create user and Ext Checked.
SIP Trunk Enable, SIP Register Enable, Auto Create Ext/User, SIP Remote Extn Enable. (All is Checked)
Domain Name: AVAYA.KADDB.COM
TLS checked
User >> Power User, Enable One-X Portal Service, Enable Remote Worker, Enable Mobile VOIP Client.

Seeking for your kind response..Thank you..
Reply With Quote
  #2  
Old 04-03-2017, 04:11 PM
mqatatsheh mqatatsheh is offline
Brainiac
 
Join Date: Dec 2012
Posts: 67
mqatatsheh has 10 reputation points
Default Avaya IPO One-X throug VPN

Hi ...
Any help ?
Reply With Quote
  #3  
Old 04-06-2017, 06:51 AM
smith1075 smith1075 is offline
Member
 
Join Date: Jul 2010
Posts: 8
smith1075 has 11 reputation points
Default

From recollection your XMPP and SIP domain should be different and you should have local DNS entries pointing to the internal IP addresses of your IP500 and Application Server/One X Portal
Reply With Quote
  #4  
Old 04-10-2017, 12:26 AM
kirchenlo kirchenlo is offline
Guru
 
Join Date: Nov 2010
Posts: 195
kirchenlo has 15 reputation pointskirchenlo has 15 reputation points
Default

Please check out the VoIP Client sub menu within the IP Office Kno0wledgebase. It really good explains how it works.

Administering Avaya one-X® Mobile for IP Office:
http://marketingtools.avaya.com/know...formation.html

http://marketingtools.avaya.com/know...te_worker.html

I would use an SBC as this makes your life easier for the deployment. I found out that working via VPN and or Firewall of the customer is always a pain.
Reply With Quote
  #5  
Old 04-18-2017, 12:51 PM
mqatatsheh mqatatsheh is offline
Brainiac
 
Join Date: Dec 2012
Posts: 67
mqatatsheh has 10 reputation points
Default Avaya IPO One-X throug VPN

Hi All ...

really its fist time configure One-X mobile in VOIP mode, and customer need the One-X mobile to be run internal the network not from the external, again here is the configuration:

Here is My topology:

172.26.0.254 is IPO 9.1 Address
172.16.0.131 is One-X Portal Server

Here is My Configuration:

1. One-X Portal Server
- XMPP: 172.16.0.131

2. IP Office > System > LAN1 > VOIP
- H.323 GateKeeper Enable (tick)
- SIP Trunk Enable (tick)
- SIP Register Enable (tick)
- SIP Remote Extn Enable (tick)
- Domain name: 172.16.0.131
- UDP, TCP (tick), TLS(Untick)
IP Office > System > LAN1 > VOIP
- Media: Disabled, Strict SIPS (Untick)

3. User Extn:
- Profile: Power User (Enable One-X Portal Service, Enable Mobile VoIP Client, Enable Remote Worker)

4. One-X Mobile
*Server ID and User account:
- Server ID: 172.16.0.131
- User name: Extn Number
- Password : User Password
*Validate Server Certificate (Untick)
*Voice Over IP:
- VOIP Operation Mode: try between always, Wifi only
- Codec Preferences: Wi-Fi Codec list, Mobile network codec list ( G726,ISAC - Untick-)
*Advanced:
- Secure connection (tick)

5. on the phone screen:
- yellow triangle (Partially connected)
- error sign: VoIP Registration Failed: The application is operational with expection of the VoIP feature, which is experiencing
problems registering with the server. (Error: 3:0)
- The Mode is set to voip

Please let me to know what should I do next ? Iam very new and next step by step instruction ?

Last edited by mqatatsheh; 04-18-2017 at 12:56 PM. Reason: adding attatchment
Reply With Quote
  #6  
Old 04-18-2017, 12:53 PM
mqatatsheh mqatatsheh is offline
Brainiac
 
Join Date: Dec 2012
Posts: 67
mqatatsheh has 10 reputation points
Default Avaya IPO One-X throug VPN

Hi All ...

I found this error in log-commander file, but acctually I cant understand it (Socket (61) has an error: SOCKET: Transport endpoint is not connected (107)) and I dont know if this cause the partially connected.

04-18 13:53:19.503 D/ClientPlatform(17610): Event loop Poll(9993) processing CONNECT on socket 61
04-18 13:53:19.503 D/ClientPlatform(17610): Socket (61) connected.
04-18 13:53:19.503 D/ClientPlatform(17610): Socket (61) has an error: SOCKET: Transport endpoint is not connected (107)
04-18 13:53:19.503 D/ClientPlatform(17610): Socket (61): Reporting connection error
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPConnection::OnSocketConnectionError
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPConnection::OnSocketError
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPConnection::StartReconnectTimer(): Armed m_pReconnectTimer for 46680ms
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::OnConnectionGroupConnectionFailed(): tcp://172.16.0.131:5060 Err=SOCKET: SOCKET: Transport endpoint is not connected (107)
04-18 13:53:19.503 D/ScsCommander(17610): (85299)ScpVoipToolkit::nCallbacksPending
04-18 13:53:19.503 D/ScsCommander(17610): (85299)CountingWakeLock:::acquire before: 2
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPFeatureManager[360]:estroyFeatures()
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::IsUnregistered() returns 1
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::SearchingOnExit
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::SearchingOnEntry
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScsPlatformServicesImpl:::doReleaseWakeLock handle: 3 currentHandle: 4 counter 2 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::OnConnectionGroupDisconnected()
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::OnConnectionGroupManagerDisconnected()
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::SearchingOnExit
04-18 13:53:19.503 D/ScsCommander(17610): (1)CountingWakeLock:::release before: 3
04-18 13:53:19.503 D/ClientPlatform(17610): CSIPIdentity[360]::SearchingOnEntry
04-18 13:53:19.503 D/ScsCommander(17610): (1)CountingWakeLock:::release elapsed:29 cumulative:234354 longest:15543 release delta:0
04-18 13:53:19.503 E/ClientPlatform(17610): Failed to shutdown socket(61) errno=ENOTCONN - ignore
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScpVoipToolkit::nCallbacksPending thread processing
04-18 13:53:19.503 D/ClientPlatform(17610): ~Socket()
04-18 13:53:19.503 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::setAlarm delay: 46679 key: -771700704 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.503 W/ScsCommander(17610): (1)ScpVoipToolkit::nConnectionUnavailable server tcp://172.16.0.131:5060
04-18 13:53:19.503 W/ScsCommander(17610): (1)ScpVoipToolkit::nAllConnectionsUnavailable
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScpVoipToolkit::nRegistrationError com.avaya.clientplatform.IdentityImpl@be4dc79 error CONNECTION_ERROR
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScpVoipToolkit:::ScsCommander:OnRegistrationFai led+Scpvoiptoolkit
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScpVoipToolkit::nRegistrationErrorThread com.avaya.ScsCommander.voip.VoipRegistrationError@ a34edbe
04-18 13:53:19.503 D/ScsCommander(17610): (1)ScpVoipToolkit:::endCallsThread com.avaya.ScsCommander.voip.VoipCallError@755dcca
04-18 13:53:19.503 D/ScsCommander(17610): (1)VoipManager:::voipTkRegistrationFailed com.avaya.ScsCommander.voip.VoipRegistrationError@ a34edbe code 0 reason: Connection Error
04-18 13:53:19.503 D/ScsCommander(17610): (1)VoipManager:::announceVoipUnregistered
04-18 13:53:19.503 D/ScsCommander(17610): (1)VoipFrameworkRegisteringState:::voipTkRegistrat ionFailed com.avaya.ScsCommander.voip.VoipRegistrationError@ a34edbe code 0 reason Connection Error
04-18 13:53:19.503 D/ScsCommander(17610): (1)CountingWakeLock:::acquire before: 2
04-18 13:53:19.503 D/ScsCommander(17610): (1)FiniteStateMachine:::FSM 'VoipManagerFsm' transitioning states: VoipFrameworkRegisteringState->VoipFrameworkRegistrationFailedState
04-18 13:53:19.503 D/ScsCommander(17610): (1)VoipManager:::disarmTimer
04-18 13:53:19.503 D/ScsCommander(17610): (1)InsomniousTimer:::disarmTimer
04-18 13:53:19.503 D/ScsCommander(17610): (1)InsomniousTimer:::disarmTimer action: com.avaya.ScsCommander.voip.VoipManager.TIMER_INTE NT.com.avaya.ScsCommander.utils.InsomniousTimer@9e 99172
04-18 13:53:19.513 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::releaseWakeLock handle: 4 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.513 D/ScsCommander(17610): (1)VoipFrameworkRegistrationFailedStateAbstract::: doEntryAction
04-18 13:53:19.513 D/ScsCommander(17610): (1)VoipManager:::armTimer in ms: 20000
04-18 13:53:19.513 D/ScsCommander(17610): (85299)CountingWakeLock:::acquire before: 3
04-18 13:53:19.513 D/ScsCommander(17610): (1)InsomniousTimer:::armTimer in ms: 20000 wake: 0 action: com.avaya.ScsCommander.voip.VoipManager.TIMER_INTE NT
04-18 13:53:19.513 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::getWakeLock handle: 5 counter 1 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.513 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::cancelAlarm 4 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.513 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::setAlarm delay: 46666 key: -771700704 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.523 D/ScsCommander(17610): (1)CountingWakeLock:::release before: 4
04-18 13:53:19.523 D/ScsCommander(17610): (1)CountingWakeLock:::release elapsed:49 cumulative:234354 longest:15543 release delta:0
04-18 13:53:19.523 D/ScsCommander(17610): (1)ScpVoipToolkit:::removeIdentity
04-18 13:53:19.523 D/ScsCommander(17610): (1)CountingWakeLock:::release before: 3
04-18 13:53:19.523 D/ScsCommander(17610): (1)CountingWakeLock:::release elapsed:49 cumulative:234354 longest:15543 release delta:0
04-18 13:53:19.523 D/ScsCommander(17610): (1)AppLifeCycleMonitor::nReceiveBroadcastIntent com.avaya.ScsCommander.voip.VoipManager.VOIP_UNREG ISTERED
04-18 13:53:19.523 D/ScsCommander(17610): (1)VoipStateTracker:::Broadcast RXed: com.avaya.ScsCommander.voip.VoipManager.VOIP_UNREG ISTERED
04-18 13:53:19.523 D/ScsCommander(17610): (1)VoipStateTracker:::setVoipStatus unregistered
04-18 13:53:19.523 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::releaseWakeLock handle: 5 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.523 D/ScsCommander(17610): (85299)CountingWakeLock:::acquire before: 2
04-18 13:53:19.523 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::getWakeLock handle: 6 counter 2 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.523 D/ScsCommander(17610): (85299)ScsPlatformServicesImpl:::cancelAlarm 5 com.avaya.flare.ScsPlatformServicesImpl@2976127
04-18 13:53:19.523 D/ClientPlatform(17610): CSIPIdentity[360]::ShutdownInternal: Graceful shutdown = no
04-18 13:53:19.523 D/ClientPlatform(17610): CSIPFeatureManager[360]:estroyFeatures()
04-18 13:53:19.523 D/ClientPlatform(17610): CSessionMgr[360]:ShutdownInternal: no
04-18 13:53:19.523 D/ClientPlatform(17610): CSessionMgr[360]:RemoveRemoteSessions
04-18 13:53:19.523 D/ClientPlatform(17610): CSIPConnectionGroup::RemoveAllConnections(): Number of connections = 1
04-18 13:53:19.523 D/ClientPlatform(17610): CSIPConnection::Cleanup(): Disabled m_pReconnectTimer

Thanks you ...
Reply With Quote
  #7  
Old 01-06-2019, 12:50 AM
mjinna mjinna is offline
Aspiring Member
 
Join Date: Aug 2014
Posts: 1
mjinna has 10 reputation points
Default

Quote:
Originally Posted by kirchenlo View Post
Please check out the VoIP Client sub menu within the IP Office Kno0wledgebase. It really good explains how it works.

Administering Avaya one-X® Mobile for IP Office:
http://marketingtools.avaya.com/know...formation.html

http://marketingtools.avaya.com/know...te_worker.html

I would use an SBC as this makes your life easier for the deployment. I found out that working via VPN and or Firewall of the customer is always a pain.
Can you share any simple document to setup Onex portal with SBC in ip office environment for mobile users over 3G.
My email jinnamohd@gmail.com
Thanks in Advance

Last edited by mjinna; 01-06-2019 at 12:51 AM. Reason: Not full
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:27 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.