- Community Home
- >
- Networking
- >
- Legacy
- >
- IP Telephony - NBX
- >
- Dial Plan On VTL
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2011 01:26 PM
02-01-2011 01:26 PM
Dial Plan On VTL
My customer has 2 NBX 3000 located in city A and City B, He wants to make local calls from city B to city A, Today is configured the dial plan with the extension numbers on each site with VTL's, but I don't know what I have to modified in dial plan in site B to dial a local call in site A. Can you tell me how do I have to configure both dial plans to dial from B to A dialing local numbers in A and in A how is modified the dial plan to receive the digits.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 08:56 AM
02-03-2011 08:56 AM
Re: Dial Plan On VTL
That takes a little bit of work . I suggest you start by using our knowledgebase , and then see the documents on how to .
You must set up a route fro Site a to site b with the IP address of site b in the route . Then assign that route to table one for the extensions at site b using the new route created
Outside lines you must set the same thing up on a different route on table 2 so that when you dial the did direct or you use an AA , it knows how to get over to site b ( Table 2 is inbound and outbound - NOT internal )
Making outbound calls requires you to set up a password for what is called hop off , so you need to determine :
1. Internal calls or extenral calls or both ?
2. seperate routes for internal calls and extenral calls due to password for outboudnc alls .
This is to start with .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 10:15 AM
02-03-2011 10:15 AM
Re: Dial Plan On VTL
The NBX Admin Guide really does a great job in explaining the dialplans for VTL.. please check that out... it
also has examples.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 10:28 AM
02-03-2011 10:28 AM
Re: Dial Plan On VTL
I need the syntax of the dial plan in both sites, to send the digits to dial outbound and in the site the receives the digits and take a trunk to make the call outbound. Do you have something of hop on and hop off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 10:29 AM
02-03-2011 10:29 AM
Re: Dial Plan On VTL
Thanks, I have read the manual it says and talk about the VTL hop on and hop off, but it doesn't say how does the dial plan has to be writed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 11:18 AM - edited 02-03-2011 11:31 AM
02-03-2011 11:18 AM - edited 02-03-2011 11:31 AM
Re: Dial Plan On VTL
Not as easy as it looks but here are the syntaxes for internal NBX to NBX dialing .
Build your routes
Then after you build them assign them to the digits in table one or two that you wish to reroute to the vtls .
I ioncluded a sample dial plan in the attachements section of this post as well ....
Table Create 1 Internal 4 Digit Extensions
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 1 1 0 1 1 Internal 0 4
TableEntry Create 1 2 1 4 4 WAN 0 12
TableEntry Create 1 3 2 4 4 WAN 0 10
TableEntry Create 1 4 3 4 4 WAN 0 17
TableEntry Create 1 5 4 4 4 WAN 0 11
TableEntry Create 1 6 500 3 3 Internal 0 3
TableEntry Create 1 7 55 4 4 Internal 0 3
TableEntry Create 1 8 6 4 4 Internal 0 0
TableEntry Create 1 9 7 4 4 Diagnostics 0 0
TableEntry Create 1 10 9 10 11 Local 0 1
Table Create 2 Incoming 4 Digit DID and Auto At
/ Id Entry Digits Min Max Class Prio Route
/ -- ----- ------------ --- --- ------------- ---- -----
TableEntry Create 2 1 0 1 1 Internal 0 4
TableEntry Create 2 2 1 4 4 WAN 0 12
TableEntry Create 2 3 2 4 4 WAN 0 10
TableEntry Create 2 4 3 4 4 WAN 0 17
TableEntry Create 2 5 4 4 4 WAN 0 11
/ Route Description
/ ----- -----------
DestinationRoute Create 1 LocalCO
DestinationRoute Create 2 LocalCONoStrip
DestinationRoute Create 3 Voice Application
DestinationRoute Create 4 Attendant
DestinationRoute Create 5 H323 ConneXtions Ports
DestinationRoute Create 6 Virtual Tie Line (VTL) Ports
DestinationRoute Create 7 Reserved
DestinationRoute Create 8 8 Pool
DestinationRoute Create 9 Reserved
DestinationRoute Create 17 Birmingham VTL Connection
DestinationRoute Create 10 Mobile VTL Connection
DestinationRoute Create 11 Orlando VTL Connection
DestinationRoute Create 12 Accellera VTL Connection
/ Route Entry DestinationExtension
/ ----- ----- --------------------
DestinationRouteEntry Create 1 1 *0001
DestinationRouteEntry Create 1 2 *0002
DestinationRouteEntry Create 2 1 *0001
DestinationRouteEntry Create 2 2 *0002
DestinationRouteEntry Create 3 1 *0003
DestinationRouteEntry Create 4 1 *0004
DestinationRouteEntry Create 5 1 *0005
DestinationRouteEntry Create 6 1 *0006
DestinationRouteEntry Create 7 1 *0003
DestinationRouteEntry Create 8 1 *0008
DestinationRouteEntry Create 9 1 *0003
DestinationRouteEntry Create 17 1 *0006
DestinationRouteEntry Create 17 2 *0001
DestinationRouteEntry Create 10 1 *0006
DestinationRouteEntry Create 11 1 *0006
DestinationRouteEntry Create 12 1 *0006
/ Route Entry OperId Operation Value
/ ----- ----- ------ --------- -----
DestinationRouteOperation Create 1 1 1 stripLead 1
DestinationRouteOperation Create 1 2 1 stripLead 1
DestinationRouteOperation Create 8 1 1 stripLead 1
DestinationRouteOperation Create 17 1 1 prepend 192*168*1*190*
DestinationRouteOperation Create 17 2 1 stripLead 4
DestinationRouteOperation Create 17 2 2 prepend 818883005132
DestinationRouteOperation Create 10 1 1 prepend 192*168*25*190*
DestinationRouteOperation Create 11 1 1 prepend 192*168*7*190*
DestinationRouteOperation Create 12 1 1 prepend 10*10*10*190*
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2011 11:22 AM
02-03-2011 11:22 AM
Re: Dial Plan On VTL
Take a look at page 351-354 in the NBX 6.5 Admin Guide (Configuring VTL passwords in the Dialplan)
Remember that the IP address will always be stripped on the receiving end by the NBX and it will hit Table 1,
so whatever you have in table 1 is good.
FOr example, suppose system A is 10.1.1.1 and system B is 10.2.2.2.
System A user dials 31918885551212 (where in table 1, the site code of System B is 31)
System A is set up to striplead 2 and add the System B IP address.
So System A will then send 10*2*2*2*password*918885551212,
Now System B automatically strips the IP address (don't need to do anything in the dialplan) and you the call hits Table 1 and System B will then dial out 918885551212
it is tough to put this in the Forum notes, but I hope this helps !!!!