Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP_Office_AVAYA_PushNotification_OK_IphoneClient_Rings_But_call_Error

Status
Not open for further replies.
DNapoles

DNapoles

Technical User
Joined
May 30, 2022
Messages
9
Location
IT
AVAYA IP 500V2 - version 11.1.2.4 build 18, Avaya Push notification correctly configured, non errors from System Status. AVAYA Workplace ver. 3.38 installed on Iphone 14, you call the extension, the APNP wakes up the extension (from System Status you see the extensions registered from IP private address because the Iphone is connected to wifi), then the phone rings you try to answer but you can't answer because the app shows "Call error".
So how can it be possible?

Thanks

DN
 
Solution
DNapoles
Hello
derfloh said:
Even this error message look like a config error (wrong domain in the client settings) it is most likely that the SIP domain is not part of the server certificate's SANs (subject alternative names).

You will have to have a certificate that has the FQDN and the SIP domain as DNS entry.
Click to expand...
Hello derfloh,

the SIP domain was part of the server certificate's SANs (subject alternative names) that I've regenerated. But anyway there was clearly a problem with the certificate SSL.

2025-02-06 09:34:29,962 WARN [CSDKEventLoop] - [ClientSDK] > [SECURITY] WARN CCertificateManagerSecurityLogger::LogCertificateValidationResult(): [Request id = 18] Certificate validation posses additional failure information: "Server identity validation failed because service...
Sort by date Sort by votes
I guess it's not a push notification issue and you will be able to reproduce it with workplace app open and registered.

In this case, you should check the SIP messages.

For me it sounds like that the firewall is not able to reach the client am the time or the mobile phone's ISP is blocking something.

Do you use TLS or TCP signaling?
 
Upvote 0 Downvote
We have a similar issue
Are you using the Avaya SBC?
Our issue is often times the call will only ring about a half ring and cannot be answered. But subsequent calls can.
Is your issue on every call or just once in a while?
 
Upvote 0 Downvote
If using an ASBCE, try adding FORCE_SIP_SBC_TCP_SINGLE_PORT as a NUSN.
 
Upvote 0 Downvote
Indeed derfloh the push notification service is working very well. I think it's about signaling as you said.
I was using TCP signaling, instead of TLS.

Last night, I've changed to TLS singnaling but the extension 228 on app AVAYA Workplace didn't get registered, because of Login failed. Invalid domain



PRN: Service Access Connection from X.X.X.X (23587) to Port 411 allow=1
HTTP: X.X.X.X (23587) - (411) HTTPSession (Secure) (Total = 2)
HTTP: X.X.X.X (23587) - (411) HTTPSession: Operational
Sip: SipTCPUser 26 incoming f19d5c64 created local 172.16.50.2:5061 remote X.X.X.X:1140 list size 17
Sip: SIPPhoneReceiver 444 (f19d639c) tcp created, srcaddress X.X.X.X:1140, list size 21
Sip: SipTCPUser 26 incoming f19d5c64 TCP established secure 1 operational 0
HTTP: X.X.X.X (23587) - (411) HTTPSession: TLSOperational using cipher=c014 resumed=false
Sip: SipTCPUser 26 incoming f19d5c64 TLSOperational using cipher=c027 resumed=0
Sip: SIPPhoneReceiver 444 disconnectIndication from tcp, srcaddress X.X.X.X
Sip: SipTCPUser 26 incoming f19d5c64 destroyed list size 16 secure 1 oprational 1
Sip: SIPPhoneReceiver 444 (f19d5c64) destroyed, srcaddress X.X.X.X:1140, list size 20
HTTP: Secure Rx Src: X.X.X.X(23587)-(411)
GET /tpkt/mtcti HTTP/1.1
User-Agent: Avaya Communicator Android/3.38.1 (FA-RELEASE84-BUILD.14; SNE-LX1)

HTTP: X.X.X.X(23587)-(411)HTTPServerSessionIO: DNS address resolved for FQDN=avaya.customerdomain.com IP=X.X.X.X dns_retries=0
PRN: Not accepting mtcti WebSocket request from 228 - too many clients
HTTP: Secure Tx Dest: X.X.X.X(23587)-(411)
HTTP/1.1 401 Unauthorized


HTTP: Secure Rx Src: X.X.X.X(23587)-(411)
GET /tpkt/mtcti HTTP/1.1
User-Agent: Avaya Communicator Android/3.38.1 (FA-RELEASE84-BUILD.14; SNE-LX1)


HTTP: X.X.X.X(23587)-(411)HTTPServerSessionIO: DNS address resolved for FQDN=avaya.customerdomain.com IP=X.X.X.X dns_retries=0
PRN: Not accepting mtcti WebSocket request from 228 - too many clients
HTTP: Secure Tx Dest: X.X.X.X(23587)-(411)
HTTP/1.1 401 Unauthorized

Thank you
 
Upvote 0 Downvote
finest said:
We have a similar issue
Are you using the Avaya SBC?
Our issue is often times the call will only ring about a half ring and cannot be answered. But subsequent calls can.
Is your issue on every call or just once in a while?
Click to expand...
No, I am not using the AVAYA SBC I am using AVAYA IP 500V2 with AVAYA Spaces.
Unfortunately once in a while.
 
Upvote 0 Downvote
sizbut said:
If using an ASBCE, try adding FORCE_SIP_SBC_TCP_SINGLE_PORT as a NUSN.
Click to expand...
No, I am not using the AVAYA SBC I am using AVAYA IP 500V2 with AVAYA Spaces.

Thanks, anyway!
derfloh said:
I guess it's not a push notification issue and you will be able to reproduce it with workplace app open and registered.

In this case, you should check the SIP messages.

For me it sounds like that the firewall is not able to reach the client am the time or the mobile phone's ISP is blocking something.

Do you use TLS or TCP signaling?
Click to expand...
Indeed @derfloh the push notification service is working very well. I think it's about signaling as you said.
I was using TCP signaling, instead of TLS.

Last night, I've changed to TLS singnaling but the extension 228 on app AVAYA Workplace didn't get registered, because of Login failed. Invalid domain



PRN: Service Access Connection from X.X.X.X (23587) to Port 411 allow=1
HTTP: X.X.X.X (23587) - (411) HTTPSession (Secure) (Total = 2)
HTTP: X.X.X.X (23587) - (411) HTTPSession: Operational
Sip: SipTCPUser 26 incoming f19d5c64 created local 172.16.50.2:5061 remote X.X.X.X:1140 list size 17
Sip: SIPPhoneReceiver 444 (f19d639c) tcp created, srcaddress X.X.X.X:1140, list size 21
Sip: SipTCPUser 26 incoming f19d5c64 TCP established secure 1 operational 0
HTTP: X.X.X.X (23587) - (411) HTTPSession: TLSOperational using cipher=c014 resumed=false
Sip: SipTCPUser 26 incoming f19d5c64 TLSOperational using cipher=c027 resumed=0
Sip: SIPPhoneReceiver 444 disconnectIndication from tcp, srcaddress X.X.X.X
Sip: SipTCPUser 26 incoming f19d5c64 destroyed list size 16 secure 1 oprational 1
Sip: SIPPhoneReceiver 444 (f19d5c64) destroyed, srcaddress X.X.X.X:1140, list size 20
HTTP: Secure Rx Src: X.X.X.X(23587)-(411)
GET /tpkt/mtcti HTTP/1.1
User-Agent: Avaya Communicator Android/3.38.1 (FA-RELEASE84-BUILD.14; SNE-LX1)

HTTP: X.X.X.X(23587)-(411)HTTPServerSessionIO: DNS address resolved for FQDN=avaya.customerdomain.com IP=X.X.X.X dns_retries=0
PRN: Not accepting mtcti WebSocket request from 228 - too many clients
HTTP: Secure Tx Dest: X.X.X.X(23587)-(411)
HTTP/1.1 401 Unauthorized


HTTP: Secure Rx Src: X.X.X.X(23587)-(411)
GET /tpkt/mtcti HTTP/1.1
User-Agent: Avaya Communicator Android/3.38.1 (FA-RELEASE84-BUILD.14; SNE-LX1)


HTTP: X.X.X.X(23587)-(411)HTTPServerSessionIO: DNS address resolved for FQDN=avaya.customerdomain.com IP=X.X.X.X dns_retries=0
PRN: Not accepting mtcti WebSocket request from 228 - too many clients
HTTP: Secure Tx Dest: X.X.X.X(23587)-(411)
HTTP/1.1 401 Unauthorized

Thank you
 
Upvote 0 Downvote
Even this error message look like a config error (wrong domain in the client settings) it is most likely that the SIP domain is not part of the server certificate's SANs (subject alternative names).

You will have to have a certificate that has the FQDN and the SIP domain as DNS entry.
 
Upvote 0 Downvote
Call me stupid but you started by talking about APN and Iphone - but all the traces show Android!
 
Upvote 0 Downvote
Hello
derfloh said:
Even this error message look like a config error (wrong domain in the client settings) it is most likely that the SIP domain is not part of the server certificate's SANs (subject alternative names).

You will have to have a certificate that has the FQDN and the SIP domain as DNS entry.
Click to expand...
Hello derfloh,

the SIP domain was part of the server certificate's SANs (subject alternative names) that I've regenerated. But anyway there was clearly a problem with the certificate SSL.

2025-02-06 09:34:29,962 WARN [CSDKEventLoop] - [ClientSDK] > [SECURITY] WARN CCertificateManagerSecurityLogger::LogCertificateValidationResult(): [Request id = 18] Certificate validation posses additional failure information: "Server identity validation failed because service domains match failed.".
2025-02-06 09:34:29,962 DEBUG [CSDKEventLoop] - [ClientSDK] > CTLSSocket::OnCertificateValidationResult() this[0x71f84d4600] Socket (275): Socket (275) monitoring for reading.
2025-02-06 09:34:29,962 WARN [CSDKEventLoop] - [ClientSDK] > [SECURITY] WARN CTLSSocket::OnCertificateValidationResult() this[0x71f84d4600] Socket (275): TLSSocket (275), Server certificate rejected.
2025-02-06 09:34:29,962 DEBUG [CSDKEventLoop] - [ClientSDK] > CSIPConnection::OnSocketConnectionError() : Connection instance = 0x721c052000 error[INVALID_SERVICE_DOMAIN_IDENTITY]

I regenerated the SSL certificate from the AVAYA IPO Security Settings and then the SIP registration in TLS works!!!

I tried to check the behavior of the extension registered on the iPhone in TLS and so far everything works correctly.

Thank you very much!
 
Upvote 0 Downvote
Solution
sizbut said:
Call me stupid but you started by talking about APN and Iphone - but all the traces show Android!
Click to expand...
Sizbut, initially there was a call error with iPhones with SIP registration in TCP which sometimes happened.

Then the signaling protocol was configured in TLS and there were registration problems due to the certificate.
 
Upvote 0 Downvote
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top