Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2000IPS Call Forward and ISDN DID

Status
Not open for further replies.

RV482

IS-IT--Management
Jun 30, 2014
130
PH
Hi!

We have a 2000IPS, some extensions are call forwarded to 1 (one) extension, how can I disable this, through MAT or is there a user code to deactivate it from there phones?

Also, how can you assign a DID number to an extension?

Thanks![bigsmile]
 
Ok so cancelling a call forward form the MAT (MatWorx) is done through command E6xx. There is also a way to cancel it from the phone but as this can be (and regularly is) changed, you would have to interrogate command 20x to find out what the code is.

Where I am in the world, we usually match the extension range to the incoming range so simply programming up an extension automatically makes it a DID. However if this is not the case on your system, you need to check out command 76.

If you don't have a manual you can use the IVS2 manual for these commands and you can download the command manual here....

 

Thanks for the assistance on the Call forward, we still have to figure out the ISDN, we also have the same approach.

Also, on command 76, all extensions are programmed with 'none' any procedure to start matching the extension to the ISDN channel. how do you identify the channels on an ISDN?

Thnaks again: D
 
You don't match extensions to ISDN channels. Typically you order a block of DID numbers from telco. Those digits are pulsed in on the ISDN span on any of the 23 voice channels. Those DID numbers usually match an extension in the system. So, no digit conversions are necessary. If they do not match, then digit conversion is done using CMD 7600/7601/7602. Each ISDN channel is programmed into the system as a trunk number in CMD 0701, then placed into a voice trunk route. The D channel is placed into a separate D channel route. CMD 0701 follows the sense wheel setting on the PRI card.
EX: sense wheel 5 (05)
0701>0500>D100
0701>0501>D101 etc.
05 = sense wheel setting
00-23 = channel number
 
Thanks for these info, unfortunately, I'm a beginner with the ISDN implementation.

Actually, the ISDN is already working, this was implemented by our former tech engineer. My challenge is to implement DIDs to other extension, the extension are the same with the ISDN channel.. e.g. our extension range 200-250, DID from telco is 245-332-xx.

Also, the newly created extension(s), when we access a dial out using the ISDN, it sends the user a message from the telco stating that 'they cannot process the call' but on the existing extensions, dial out is successful. We checked our CBS and the system sends the same telephone number format as the existing and new extensions.

Hope you could provide detailed step by step programming procedure.

Appreciate your assistance :D

THANKS!
 
DID conversion is done in CMD's 7600/7601/7602.
EX: telco sends in 250 and you want it to go to 200
7600>250>000 send incoming number to a table number 000-999.
7601>000>200 convert the number in table 000 to extension 200 in the day mode.
7602>000>200 same thing for night mode.
Trunk route data needs to be set up for 3 incoming digits and the route needs to be allowed to do digit conversion
3512>ISDN Route>2 = 3 incoming digits
3518>ISDN Route>0 = allow digit conversion.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top