INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

thread940-1753216 Avaya Communicator for Web

thread940-1753216 Avaya Communicator for Web

(OP)
Hi there!
I have managed to get this to work but only in deskphone mode.
I am running IP500V2 with a one-x portal server on a separate VM machine.

The communicator for windows works in both presence and as a softphone, with no issues even using TLS and calling the system by the name.

Does anybody got this to work by any chance?

RE: thread940-1753216 Avaya Communicator for Web

You'll need to setup WebRTC which means you need to use AppServer and not One-X on Windows.

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

RE: thread940-1753216 Avaya Communicator for Web

(OP)
Hi Janni78
Yes I do have one-x as a VM running on the CentOS.
However the media server is the ip500v2 IP Office.

Is that ok ? The release notes describe which ports to open but no schematic of what is allowed is mentioned.


RE: thread940-1753216 Avaya Communicator for Web

What release, as the docs for one release omitted one of the main ports required to make it work.

The following ports are what we configure and label as web communicator on out hosted setup firewalls.

7443
56000:57000

| ACSS SME |

RE: thread940-1753216 Avaya Communicator for Web

(OP)
I am running 9.1.9. Application server and IP Office are on the same level and release.
I have opened 7443.
I do not know about 56000:57000, are these UDP ?

RE: thread940-1753216 Avaya Communicator for Web

(OP)
Those ports in UDP are already open because they fall in the same range that the one-x mobile for IPO uses.
I have them open towards the IP500V2.

RE: thread940-1753216 Avaya Communicator for Web

On the 7070 page under Applications WebRTC configuration the RTP ports are shown they are 56000-58000 by default.

Then the softphone part requires the SIP ports as under SIP server setup forwarded through to the phone system - these should be the same as those set on the LAN1 VoIP tab.

The setup is easier on SE but I definitely have it working on one app server with a 500.

| ACSS SME |

RE: thread940-1753216 Avaya Communicator for Web

(OP)
Thanks Pepp77!
I found that the webRTC service on the application server was stopped. I didn't see that because one has to expand the list of services to find out.

I have the softphone logging in now and it also shows the same status of my deskphone whenever I make a call.
I can also see the phone registered as a SIP extension in the monitor application as an Avaya WEBRTC client with the ip originating from the application server and not the ip address of the end remote client. This means that the application server is acting as a client to the IP500 on behalf of the remote end client.

The only problem is that when I place a call the action is taken in the softphone, the party I am calling does not ring, and the softphone tries only once and hangs up.

RE: thread940-1753216 Avaya Communicator for Web

I think you need TCP/9443 to connect. But I am not sure enough to be honest.

RE: thread940-1753216 Avaya Communicator for Web

Just did this in house this week IP 500 with application server. The 9443 port does get used I missed it and saw it as unreachable in wireshark. The list of ports needed are in the installation manual. I honestly had more issues with the certificates (and my computer being dumb) then anything else.

The truth is just an excuse for lack of imagination.

RE: thread940-1753216 Avaya Communicator for Web

In 9.1.2+ you needed TCP/7443,7070,9443.
In 10.0 it uses TCP/9443 for all services.

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

RE: thread940-1753216 Avaya Communicator for Web

i think it is the 7443 port that is also needed in 10 as we definitely need it on our hosted which runs on 10.

The 9443 I missed as that was listed under the one-x ports on the firewall settings.

| ACSS SME |

RE: thread940-1753216 Avaya Communicator for Web

(OP)
Hello
Thank you for the feedback. I am ok on the ports because I am able to regsiter the chrome app successfully and presence showing ok as well.
I run a scan on the firewall and found out which ports were being used by the app.

I have this problem now...when I make a call from the Chrome APP Communicator for Web, it tries to call, but drops the call. The Call is not visible in System status, and monitor reports the following:

10.0.0.44 is the APP server,
Extn304 is the Communicator client registered extension.
21893883 is the number that I tried to call.
onex.myipo.com is the name used in the Communicator for web as a media server.


09:53:58 615022mS SIP Call Tx: phone
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/TCP 10.0.0.44:42004;branch=z9hG4bK-373337-c190d69cf89a428fef1f150e89b775f6
From: <sip:Extn304@onex.myipo.com>;tag=d25c756e
Call-ID: ffbc6e207bc14f40b09f91838a010e51@10.0.0.44
CSeq: 1 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
Server: IP Office 9.1.9.0 build 182
To: <sip:21893883@onex.myipo.com>;tag=fec72f3bd17abbd3
Content-Length: 0

09:53:58 615022mS SIP Tx: TCP 10.0.0.60:7565 -> 10.0.0.44:36325
SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/TCP 10.0.0.44:42004;branch=z9hG4bK-373337-c190d69cf89a428fef1f150e89b775f6
From: <sip:Extn304@onex.myipo.com>;tag=d25c756e
Call-ID: ffbc6e207bc14f40b09f91838a010e51@10.0.0.44
CSeq: 1 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
Server: IP Office 9.1.9.0 build 182
To: <sip:21893883@onex.myipo.com>;tag=fec72f3bd17abbd3
Content-Length: 0

09:53:58 615023mS CMExtnRx: v=304, p1=0
CMReleaseComp
Line: type=SIPLine 260 Call: lid=10001 id=1025 in=0
Cause=79, Service or option not implemented, unspecified
09:53:58 615025mS CMLOGGING: CALL:2017/09/2909:53,00:00:00,000,304,O,,,Extn304,,,1,,"",0,n/a
09:53:58 615025mS CD: CALL: 10001.1025.0 BState=Idle Cut=1 Music=0.0 Aend="Extn304(304)" (0.0) Bend="" [] (0.0) CalledNum= () CallingNum=304 (Extn304) Internal=1 Time=11 AState=Idle
09:53:58 615025mS CD: CALL: 10001.1025.0 Deleted
09:53:58 615025mS CMExtnEvt: Extn304: CALL LOST (CMCauseNormal)
09:53:58 615025mS CMExtnEvt: Extn304: Extn(304) Calling Party Number(304) Type(CMNTypeNetworkSpecific)
09:53:58 615025mS CMCallEvt: 0a00003c00000401 10001.1025.0 -1 Extn304.0: StateChange: END=X CMCSIdle->CMCSCompleted
09:53:58 615025mS CMExtnEvt: v=0 State, new=PortRecoverDelay old=Idle,0,0,Extn304
09:53:58 615026mS CMExtnTx: v=304, p1=0
CMReleaseComp
Line: type=SIPLine 260 Call: lid=10001 id=1025 in=0
Called[] Type=Default (100) Reason=CMDRdirect Calling[304] Type=NetworkSpecific Plan=Default
Cause=16, Normal call clearing
Timed: 29/09/17 09:53








@critchey - The certificates can be tricky to find out the right steps.
Get an authentic ssl certificate. You can trial using comodo, they offer free certificates for 90 days to test with.
Generate a request before you do so and make sure you keep the private key.
When you receive the certificate, upload it in both IPO and APP server by clicking "+ add Certificate"
Upload also the CA of the provider. This is downloadable from the provider of the Certificate.

Then run this from your windows command prompt to export the provided certificate to pkcs12:
"C:\ openssl pkcs12 -export -out certificate.pfx -inkey privateKey.key -in certificate.pem"
(where certificate.pfx will be the file output in the right format recognised by IPO and APP server, private.key is the private key file and certificate.pem is the certificate you receive from provider in PEM format)

If the above command gives errors such as :
WARNING: can't open config file: /etc/ssl/openssl.cnf then type the following command: "set OPENSSL_CONF=c:\[PATH TO YOUR OPENSSL DIRECTORY]\bin\openssl.cfg"
or if you get
unable to write 'random state' then type the following command: "set randfile=c:\[your PATH]\test.rnd

The command is successful when it asks you for a password.
Once you have the output file "certificate.pfx" goto your IPO and APP server

You need to access both ip office and application server on https://address:7070
Goto the certificates section. Clicm on the "SET" button and point to the new "certificate.pfx" which is the correct format in pkcs12. Type the password set during the creation from command prompt.
The full DNS name created during the request will show in the top after a successful upload. Restart both IPO and APP server.
For the certificate to be valid on your client now you need to call the system with the name as generated on the certificate.


RE: thread940-1753216 Avaya Communicator for Web

I see that I needed 7443 as well, don't know if I upgraded from 9.1 when I tested though.

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

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close