Problem With Callcentric Incoming Caller ID
carl:
It's working now.
VOIPisGreat:
Quote from: carl on October 18, 2013, 06:15:00 pm
It's working now.
Good for you, but I'm still having issues.
powaking:
I'm having the exact same problem. It was working fine up until this weekend. If I call my callcentric line directly then I get proper cname. If I call my GV which then forwards to CC then I get PRIVATE CALLER instead. In my CC logs it shows Anonymous as being received. I have not filed a ticket with CC yet.
powaking:
Received the following from CC support:
Hello,
We checked the trace logs for one of the calls and noticed the following:
Remote-Party-Id: <sip:########@xxxxxxxx;user=phone>;party=calling;id-type=subscriber;privacy=uri;screen=yes
In particular the "Privacy=uri" portion which indicates that the call is being sent to us anonymous and we should not pass the caller ID information for the call. As per the SIP RFC our servers are then stripping the CID information when sending it to your device. This is beyond our control, Google needs to change or remove the privacy flag in order for the call to be forwarded with caller ID information.
If you have any other questions please feel free to contact us at any time, thank you.
SteveInWA:
See this similar discussion:
http://www.obitalk.com/forum/index.php?topic=3640.msg43621#msg43621
If enough people who have paid and free CC DIDs would open tickets and insist that CC look into why their free and paid DIDs handle CID differently, then maybe CC will fix it on their end. Google is going to take a look at it, as of today, but I think it would be more productive if CC figured out what's different on their side.
I would call BS on CC unless they produce a similar log for an inbound call to a paid DID.
Navigation
[0] Message Index
[#] Next page
[*] Previous page