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!

Translating Extensions 1

Status
Not open for further replies.

thepfy

IS-IT--Management
Mar 20, 2006
267
GB
I'm having a bit of brain fade from working on other systems at the moment.

What is the best way to translate an extension number on an Openscape 4000?
We got some extension on another system which translate to extensions
e.g. DX Extn 24123 translates to Openscape 46123
I've got the translations on the other systems but currently callers on the Openscape dialling 24123 would go to the other system and then back again.
This is something I would like to avoid to free up trunks.

Quite a straight forward question but I believe there are multiple ways of doing it.
 
On the iSDX you would use a translation table.
On the OS4K you would use a Net Route and send the extensions to that netroute.

If an extension 1234 already exists on the iSDX and you want to copy that to send 2345 to the iSDX then:
DIS-WABE:GEN,1234;

You should see something like DESTNO=xxx
Then
CHA-WABE:2345,XXX;

 
Hi SBCSU,

Thanks but I think I may be explained it well.

On DX 24123 tranalates to 46123 on OS4K using ADTT 3 24123 46123 Y
On OS4K 24123 is set with Node Number 5 which corresponds to the DX (CHA-WABE:24123,5))

However, I want anyone who dials 24123 on a OS4K extension for it to be translated to 46123.
Currnetly any call go to the DX which translates it and then sends it back.

Thanks
 
Ok - well the quickest and easiest way is to add a 'float' number and then forward that to the new number
Example:

CHA-WABE:24123,0; (Bring number back to 4K)
ADD-SCSU:24123,,ANATE,0,0,13,1,1,1,1,1,0,1,0,10,,,,VAR,,,,ENGLISH,FLOAT,,NO,,,,0,,YES,NO,1,; (Add float number)
ADD-ACTDA:STN,24123,FWD,STATIONV,CFBNR,GEN,VCE,46123; (Forwarding of float)

Float number does not take a licence.
Add a name to the float to remind you what it was for:

ADD-PERSI:STN,24123,"Fwd->46123";
 
That will work but will affect forwards to voicemail, you'd have to associate both numbers with the same mailbox, depending on which number is sent as the redirecting party. You could also use rufum to do this. Instead of scsu and actda, you could add-rufum:did,24123,46123; which is more of a direct exchange, from one number to the other. Displays will be neater.
 
Yes but RUFUM is for Incoming number translation.
OP wants to dial outbound to an extension on another system
 
Sure, but the 4K doesn't keep separate tables for station numbers that have been dialled by trunk and numbers dialled internally. He doesn't want to dial outbound to an extension on another system, he wants to trap it and keep it internal. Rufum will work fine, without the display clutter. Just a matter of preference.
 
Indeed, however the site I am currently working on as an example - they dial 6 for a paging system yet there are direct dial in numbers beginning with 6 so yes they are in RUFUM because you can not dial them (As soon as you dial 6 you get the pager)
I only add extensions as floats for this reason and also if you need a name appearing when you dial because you can ADD-PERSI to a float and then you know what it is for.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top