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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2 DID with the same last four digit!!!!!!
- Thread starter chipig
- Start date
OzzieGeorge
Programmer
Surely you don't have 7 digit numbering on your system!!!!
what is Cmd 3512 set to for your inbound routes?
I assume you have two inbound ranges and if so they will both end up at the same extensions. However depending on how many digits (hopefully 3 or less, thats 2 or less as the data in 3512) are recieved you may be able to play tricks on the system by prefixing the two routes with different numbers and then using Cmd 76 to translate them to different numbers. I just can't remember whether the prefix takes effect before the translation or not, I would have to test it.
what is Cmd 3512 set to for your inbound routes?
I assume you have two inbound ranges and if so they will both end up at the same extensions. However depending on how many digits (hopefully 3 or less, thats 2 or less as the data in 3512) are recieved you may be able to play tricks on the system by prefixing the two routes with different numbers and then using Cmd 76 to translate them to different numbers. I just can't remember whether the prefix takes effect before the translation or not, I would have to test it.
OzzieGeorge
Programmer
Scrub that idea. Cmd 76 only applies to the recieved digits not the prefix. What you would have to do is get your carrier to supply three digits on one route and four digits (or two depending on useage) on the other and then you can differentiate in Cmd 76.
In the 2000 ivs there is no way that I have found to handle this, if you have an IVS2 or IPS then you would set for the trunk route that you will be receiving your DID's on Set 3518, 35170, 35171, 35172. ******Then remove all entries from 7600******Set your 7 digits received in command 7690, then follow normal programming from there.
OzzieGeorge
Programmer
Smoom
The tactic of getting differing digit lengths will work as Cmd 76 acts directly on the digits recieved, so in Cmd 76 you can set 8310 to one destination and 310 to another. Or so I am informed by a normally reliable source!!
Interesting that in the IPS manual you can only set 3512 to a maximum of 4 digits recieved but you can digit convert many more in cmd 76????
The tactic of getting differing digit lengths will work as Cmd 76 acts directly on the digits recieved, so in Cmd 76 you can set 8310 to one destination and 310 to another. Or so I am informed by a normally reliable source!!
Interesting that in the IPS manual you can only set 3512 to a maximum of 4 digits recieved but you can digit convert many more in cmd 76????
- Thread starter
- #6
Ok,
By the way I do have a IVS2 but I would prefer to find a way to do it without having to erase data in development table 0.Let's say I do it by setting different lenght in command 7600. How can the PBX differentiate between the two numbers if it's only looking at the last 4 digits.
688-8310 must go to station X and 780-8310 to station Y.
Can I have DID in both developoment table?
If so can table developoment 0 have 4 digits DID and Table 1 7 digits.Or I have to transfer everything to developoment table 1.
By the way I do have a IVS2 but I would prefer to find a way to do it without having to erase data in development table 0.Let's say I do it by setting different lenght in command 7600. How can the PBX differentiate between the two numbers if it's only looking at the last 4 digits.
688-8310 must go to station X and 780-8310 to station Y.
Can I have DID in both developoment table?
If so can table developoment 0 have 4 digits DID and Table 1 7 digits.Or I have to transfer everything to developoment table 1.
You would have to move everything to table 1, using MACH Script editor you could easily do a command like L7600 and save the results, then open that file using Excel or any other Spreadsheet program able to handle a CSV file change the data to 7 digits and change the 7600 line to 7690 then load the file back in, then change your Command 35 to point to table 1. As far as the 3-4 digit conversion Ozzie I tried one time on a live switch. It failed and I had to go back in a hurry so I have never played any more to find out if it would truly work. Thats something for me to setup and try sometime.
OzzieGeorge
Programmer
Smoom
It has to be arranged with the carrier for 3 digits to be sent on one and 4 on the other then for example you could have 4 digit extensions like 8300 but on incoming 76 only applies to 300 and sends it to 9300. as you are leaving 8300 set to none it wouldn't change anything and that is where it would end up. The PABX is pretty literal it only does what it is told to what is specified. It's a bit like forwarding calls to voicemail, the call ends up at the voicemail box of the dialled extension even if it has been forwarded all round the company before getting to the voicemail system. However if you have a cure that works without changes by the carrier then that is probably the way to go.
It has to be arranged with the carrier for 3 digits to be sent on one and 4 on the other then for example you could have 4 digit extensions like 8300 but on incoming 76 only applies to 300 and sends it to 9300. as you are leaving 8300 set to none it wouldn't change anything and that is where it would end up. The PABX is pretty literal it only does what it is told to what is specified. It's a bit like forwarding calls to voicemail, the call ends up at the voicemail box of the dialled extension even if it has been forwarded all round the company before getting to the voicemail system. However if you have a cure that works without changes by the carrier then that is probably the way to go.
- Thread starter
- #9
Ok,
So I went ahead and erase all 7600 DID and did a script to put them in CMD 7690.It is not working and I really do not know why.Here is What I did:
CMD 3518 = 0 ; Provide digit conversion on DID
CMD 35170 = 0; Use development table 1
CMD 35171 = 07; 7 Digits to be converted (780-8310)
CMD 35172 = 07; 7 Digits to be received
CMD 7690 for my 30 DID
Am I missing something here cause none of my DID work with CMD 7690.And also how can I be certain that my PBX is an IVS2?
So I went ahead and erase all 7600 DID and did a script to put them in CMD 7690.It is not working and I really do not know why.Here is What I did:
CMD 3518 = 0 ; Provide digit conversion on DID
CMD 35170 = 0; Use development table 1
CMD 35171 = 07; 7 Digits to be converted (780-8310)
CMD 35172 = 07; 7 Digits to be received
CMD 7690 for my 30 DID
Am I missing something here cause none of my DID work with CMD 7690.And also how can I be certain that my PBX is an IVS2?
OzzieGeorge
Programmer
The biggest single change from IVS to IVS2 is that they went from 4 digit len Numbers to 3 digit in Cmd 10. so 4 = IVS and 3 = IVS2. What is Cmd 3512 set to for your incoming routes? I ask that because if you only have 30 DID then why have 7 digits sent to you?
- Thread starter
- #11
- Status
Similar threads
- Locked
- Question