[VoiceOps] Adapting nonDIDs to a E.164 plan

Tony Zunt tony.zunt at gmail.com
Fri Jun 24 08:05:48 EDT 2016

Good morning. I could use the opinion and expertise of this group for a
quick question. I work for a large not-for-profit organization which is
coordinating dial plans for several sites. We have a contiguous block of
50K DIDs which gets us off to a nice start for an E.164 plan. We also own
about 15K other DIDs shotgunned throughout several NADP area codes, which
would also mesh nicely into an E.164 plan. Assume we are able to us ISDN
and SIP.

My question is, what is the best way to handle devices which are currently
assigned nonDIDs on our private voice network?

Obviously, they are not addressable from the PSTN now, so it's not a big
deal if they can't be called from the outside. What I am struggling with to
explain to my group is how these numbers may be best adapted to the new
plan so that they can still be called internally.

I have looked for related RFCs. I thought I found one that suggested using
a generically owned E.164 number followed by a semi-colon and the nonDID
address. I can't find the RFC now. That may work for equipment that can
form a URI like that.

I also suggested assigning a real E.164 number to these devices. Too many.

I also considered most our our IPPBXs have an intercom feature that allows
us to group and assign a locally significant address to the devices.

That might be the way to go. I'm interested to hear how other people are
doing this downtown. Is the group aware of any related RFCs we may review?

Thanks and have a great weekend!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160624/d1560070/attachment.html>

More information about the VoiceOps mailing list