09-09-2015 05:16 PM - edited 03-21-2019 08:45 AM
We use SPA508G phones with firmware 7.6.0, and the SIP->Caller ID Header is set to PAID-RPID-FROM.
In one of the call scenarios, phone sends an INVITE, server responds with an OK message that also includes a P-Asserted-Identity.
For regular non secure calls, phone displays this PAID as the caller id.
Once we set the secure calling on the phone (SIP->SRTP Method: s-descriptor, Phone->Secure Call Serv: Yes, User->Secure Call Settings: Yes), the phone starts displaying the FROM as the caller id, and not the PAID.
In both cases, server sends the PAID with the OK message.
is there anything we can do to get the phone display the PAID?
Thanks,
Matt
09-09-2015 07:58 PM
Well, it seems you hit firmware bug. In such case, no one but Cisco can help you. So call SMB Support center, report issue and wait for patched firmware.
You should be ready to provide:
Then wait for patched firmware and wish it will not take months.
In the mean time, try to set Caller ID Header to just PAID-FROM. I assume it will not help, but it cost nothing to try it. If the proxy can provide RPID you should try RPID-PAID-FROM or RPID-FROM as well.
Note you provided no detailed information to us thus this advice is based on assumption your analysis of the issue is correct.
09-09-2015 08:44 PM
Thanks Dan.
Yes, we are using SIP over TLS. Tested it without TLS also (only SRTP), and the issue still remains.
Tried PAID-FROM, and then switched to RPID on the proxy, and tried the other options as you suggested - phone is still using FROM as the caller id.
I will give support a call...
Matt
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide