Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » Avaya Client SDK - General » JS SDK: how to receive voicemail number via getVoiceMessaging()?   XML
 
Author Message
AndreyPetrov



Joined: 24/03/2021 08:39:18
Messages: 10
Offline

Hi Daniel, it could be something about your network configuration. The log you provided show some errors during the SSL handshake when AAWG try to get the voicemail number: "No subject alternative DNS name matching sipsm1.megatech-communication.de found".
AndreyPetrov



Joined: 24/03/2021 08:39:18
Messages: 10
Offline

Hi Daniel, based on the log, you may want to check your network configuration. There was an error during SSL handshake when AAWG has tried to get the voicemail number: "No subject alternative DNS name matching sipsm1.megatech-communication.de found.". Perhaps some certificate doesn't have sipsm1.megatech-communication.de in SAN (Subject Alternative Name)?

AndreyPetrov



Joined: 24/03/2021 08:39:18
Messages: 10
Offline

Hi Daniel, based on the log, you may want to check your network configuration. There was an error during SSL handshake when AAWG has tried to get the voicemail number: "No subject alternative DNS name matching sipsm1.megatech-communication.de found.". Perhaps some certificate doesn't have sipsm1.megatech-communication.de in SAN (Subject Alternative Name)?
DanielStingl



Joined: 20/11/2013 08:10:44
Messages: 32
Offline

Hi Andrey,

well, it seems that AAWG uses the https-interface to communicate with the session manager.
We have 2 certificates configured for session manager:
sips with alternative dns name sipsm1.megatech-communication.de
https with a different alternative dns name

And the certificate of the https interface was used, so that causes the warn message.
So thanks for hint. We replaced the https certificate with sips certificate and the warn message "No subject alternative DNS name matching sipsm1.megatech-communication.de found" was gone.

The following is for documentation only if someone have similar problems:
Although the above warn message was gone, the voice mail number was not yet received.
But it seems, that session manager can be contacted, because 2 more properties (IPVideoEnable, IPSoftphoneEnable) are received in JS SDK, which wasn't seen previously.
AvayaClientServices.min.js:1 [5/19/2021, 4:03:52 PM, UTC+02:00] NetworkProvider: CallGatewayProvider,
MESSAGE RECEIVED:,{
  "notification": {
    "application": "CSA",
    "contents": {
      "messageType": "EndpointConfigurationUpdate",
      "IPVideoEnable": "true",
      "IPSoftphoneEnable": "true"
    },
    "resource": "https://tkwebgw.megatech.local:443/csa/bsid/fc947647-f1ea-440d-b898-fb6ce1dcfe3e/resources/tenants/default/users/self/clients/fc947647-f1ea-440d-b898-fb6ce1dcfe3e/calls",
    "service": "telephony",
    "version": "1"
  }
}


In the logs I saw, that our secondary session manager was also involved, but no warn or error message appeared in logs.
So we also changed the https-interface certificate of the secondary session manager.
Then, voice mail number was not received.
In AAWG we cleared the AADS cache, but no luck.
We restared AAWG and now the voice mail number was received! Yeah.


Andrey, many thanks for your help!
Maybe you can induce to update the AAWG documentation how the certificate have to be configured in https interface.
In documentation it's shown that AAWG communicates via SIP with session manager, but the certificate of the https-interface was used. That is a little confusing.


Thanks for your time!
Daniel
 
 
Go to: