http://www.dslreports.com/forum/Voipms-That-number-has-not-yet-been-assigned-27719244 en Tue, 21 May 2013 08:05:13 EDT Tue, 21 May 2013 08:05:13 EDT http://www.dslreports.com/forum/Re-Voipms-quotThat-number-has-not-yet-been-assignedquot-27720056
1) The DID I'm calling is a business line that's been in existence for years, and it was doing it on all numbers I call.

2) It's not routing in my system, as this is on outbound calls I'm talking about. It's not my system that's playing that message, as it's clearly that Alison Asterisk sounding woman not the Cisco sound.

Works now just weird that it would happen for a few mins.]]> http://www.dslreports.com/forum/Re-Voipms-quotThat-number-has-not-yet-been-assignedquot-27720056 Mon, 12 Nov 2012 15:22:30 EDT http://www.dslreports.com/forum/Re-Voipms-quotThat-number-has-not-yet-been-assignedquot-27719958
1. This is a new DID and routing from other carriers may not be complete, meaning the calling party needs to notify their carrier, or,
2. Your internal routing on your phone system does not recognize the inbound DID being sent. This should be in your logs as "no destination".

You can verify both of these by viewing your inbound logs on VoIP.ms.]]> http://www.dslreports.com/forum/Re-Voipms-quotThat-number-has-not-yet-been-assignedquot-27719958 Mon, 12 Nov 2012 14:48:17 EDT http://www.dslreports.com/forum/Voipms-That-number-has-not-yet-been-assigned-27719244 http://www.dslreports.com/forum/Voipms-That-number-has-not-yet-been-assigned-27719244 Mon, 12 Nov 2012 10:52:55 EDT