I hate to post a vendor related question here but,…bandwidth.com will not answer any questions that involve Asterisk or any other PBX if they can help it.
The problem is that I have 2 Sip trunks with them, and each has it’s own local number. These work fine.
However, I also have some 800 and 866 numbers that I ported to them for DID. When someone calls one of these numbers from the outside they get NO inbound Caller ID Name. All you see is the number. This is the case with the phones and CDR reports.
Has anyone worked with bandwidth.com and seen or solved this problem? They practically hung up on me when I asked them about it.
If you mean Bandwidth.com the answer is YES. The tech I spoke with said they had nothing to do with inbound caller ID. She blamed it on Asterisk and said they don’t provide any PBX support.
Had this been my other carrier, Callcentric.com, I think I would have an answer. They don’t do phone support but they have extensive knowledge of Asterisk and gladly help with any Asterisk based issues that might be related to the specifics of their service.
I only use Bandwidth.com because they guarantee “Outbound cnam” for telemarketing legalities and such. How ironic that they won’t answer to a problem about “Inbound cnam”.
Robert Ellis at Bandwidth.com stated that for Bandwidth.com at least, toll frees will not be supported with inbound caller ID, meaning, that you won’t know who is calling your toll free numbers. After many customers complained of missing or incomplete caller ID being received for inbound calls, on October 20, 2010, Mr. Ellis confirmed in writing that quote, TF does not support caller ID period" . As to why, no reason was given, however, I was able to confirm with a customer in Dallas Texas that indeed caller ID information had disappeared from inbound calls starting Oct. 15th, 2010 without any notice whatsoever. A customer in Virginia stated he was told [by a Bandwidth.com tech] the problem was his [the customer’s]issue and not Bandwidth.com’s. Needless to say, some unsuspecting Bandwidth.com customers were surprised by calls arriving without any name information when the day started on that Friday morning. A quick wireshark trace confirmed that SIP packets were being delivered with either blank CNAM information in an incomplete PAI field, or the From, RPID, and PAI fields were incomplete and missing some part of the identify information. Unfortunately for so many customers, this means having to switch SIP providers, which is bad for Bandwidth.com and their customers, but good for their competition. One Bandwidth.com customer was quoted as saying he “hoped they [Bandwidth.com] would realize caller id is a feature that has been around for a long time and losing caller ID is like going back to the olden days when all you had was an ugly 60’s green colored analog phone. I am hopeful someone in management [at Bandwidth.com} will realize the value of providing services that customers want and need, because up to this point, they [Bandwidth.com] seemed to be forward looking and now, well, let’s just say, back to the future should stay in the movies. If we don’t get the basic features that what we want from Bandwidth.com, we’ll have to switch to another SIP provider.”