Hey Mike, hopefully 8.1.3 will resolve the issue, and/or the push service getting built into Session Manager. Right now we're waiting on Telco. The BP and Avaya have boiled it down to this:
There is no Calling name, the Calling number is there. The missing calling name is being replaced by calling number (PAI, Contact, From) in the Invite. There is not much we can do if the Vendor isn't sending the Calling Name.
2020-12-29 13:30:35.963 D [csdkloop] [CSDK] RemoteCall[8811@mydomain.net+291740996]: ReadRemoteAddressInformation(): Display name is empty. Fill the display name with remote address handle.
2020-12-29 13:30:35.963 D [csdkloop] [CSDK] RemoteCall[8811@mydomain.net+291740996]: ReadRemoteAddressInformation(): Remote display name: 916***3952, Remote address: sip:916***3952@mydomain.net
We don't care about inbound calling party name on our PRI's, but apparently if that field is empty, Avaya Web Gateway is designed to input the name field with the remote address handle, as seen by Session Manager. That seems bananas to me, because it's a useless name. Why wouldn't it default to the calling party's number?
Original Message:
Sent: 03-09-2021 10:11 AM
From: Michael Goodwin
Subject: Bad Caller ID using Web Gateway push to Workplace on iOS devices
Not the only one - I have the same style caller ID in my ios client's call history. I'm working to upgrade to 8.1.3 as well to get eliminate the web gateway for the PNS. wondering if that will change the caller-ID?
I went back and forth with my BP as well, but other issues took precedence - lol
>mike
------------------------------
Michael Goodwin
Sr Comm Engineer
Toll Brothers, Inc.
Original Message:
Sent: 02-10-2021 01:33 PM
From: Chip Powell
Subject: Bad Caller ID using Web Gateway push to Workplace on iOS devices
Scenario: Outside number (555) 123-4567 dials our user's enterprise DID. On the J series SIP phone, and on an Android phone, we see the normal "5551234567" number pass through. On Apple devices, using Web Gateway for push notification, the caller ID comes in as "sip:5551234567@mycompany.com"
We've spent a lot of time with the business partner and also Avaya on this, with much tracing and testing. What we finally got back from Avaya was that the LEC is not sending a Calling name, only the Calling number. The missing calling name is being replaced by calling number (PAI, Contact, From) in the Invite. They are pointing me to my LEC to solve, saying their hands are tied. However, when we turn Push Notification off, the problem goes away (but then we have other problems...hence the Web Gateway, the functionality of which is apparently now built into Session Manager in 8.1.3).
Have any of you experienced this? Are we the only ones?
Thanks!