[VoiceOps] Malformed Caller ID

[Guillermo Sandoval]

Ran into this issue a long time ago, make sure you're passing callerID
strictly in E.164 format

On our end, it was only really an issue when calling into some rural
telecom companies and the virgin islands.



On Thu, Apr 22, 2021 at 5:05 PM Mike Hammett <voiceops at ics-il.net> wrote:

> Have any of you noticed an increase in customer complaints of malformed
> caller ID?
>
> We do a test call out as the customer, whether it's to one of our cell
> phones or one of the incumbent's POTS lines. Everything shows up as
> expected. The number is formatted correctly. The Caller ID name is
> formatted correctly.
>
>
> However, we're getting customer complaints that the caller ID is saying
> Japan (we have nothing to do with Japan), United States, blank, or some
> other combination. We're just not able to confirm that.
>
> Of course customers are reluctant to tell us what the numbers are of the
> remote parties having these issues, so we can't really look for common
> denominators.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> Midwest Internet Exchange
> http://www.midwest-ix.com
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20210422/2fb1eccb/attachment.htm>