voip.ms Caller ID Issue

patlaw

We have a DID on voip.ms that forwards to a cell phone. Earlier today, incoming calls show that some of the calls are from Thailand. They are not. We finally answered one, and it was a legitimate call for the business. I checked the incoming call log for the number, and all of the Caller IDs there appear to be correct. Therefore, my guess is that there is something strange going on between voip.ms and the cell phone company. How would I go about positively identifying the source of the problem? It could go away on its own.

Stewart

Just guessing that your caller was from area code 660, 661, 662, 664, 667 or 669. If VoIP.ms sent the number as 10 digits to a tandem carrier that assumes E.164 format (even without a leading +), your cell carrier would display a Thai number.

For example, [+1] 662-345-6789 is a valid number in Tutwiler, Mississippi, US (never been, wouldn't want to go), while [+] 66 2 345 6789 is a valid number in Bangkok (I'm here and it's great).

If you open a ticket with VoIP.ms, they can probably tell you who their upstream was for the outbound leg of a problematic call, and what format they used for the caller ID. Ideally, they should send starting with +1, so there is no possible ambiguity.

patlaw

Thanks for the response. I'm sure that's the problem. Who fixes it? voip.ms?

Stewart

Sure. If they are using an upstream that interprets all calling numbers as beginning with the country code, they should prefix a 1 or +1 on those calls.

px_eliezer_

Stewart

Good to see you!