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 MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outgoing CLI issue

Status
Not open for further replies.

DancingDave

Technical User
Aug 11, 2003
341
GB
We have a CS1000E with Succession 5.5. Switch is located in UK, but we have an office in Germany with local PSTN.

Prior to migrating the office to VoIP, they had a mix of 3 and 4 digit extension numbers (I know!) e.g. you could have one three digit extension (e.g. 100) or ten four digit extensions (1001, 1002, 1003,....1009). This was hard enough to accommodate into our five digit dial plan (they all now have 42XXX), but now the outgoing CLI is not dialable e.g. 12345 100 is now 12345 42100.

The exchange seems to be appending 12345 to the extension number it sees from the switch.

Some are even more perverse due to their old numbering scheme e.g. 12345 201 might be 12345 42876 (the IDC table is very large!).

Is there any way that we can define the old extension number when they dial out such that e.g. 42100 shows 100 to the exchange (which would then append 12345)? One of the local engineers thought you could allocate a CLI table to each DN, but is this possible? Are there any limits on the number of such tables (we would need at least 40 of these setting up, the rest would probably make do with a presentation number).

Danke schon in advance

DD
 
You could create a unique CLID table and assign to each set. The system will allow 4000 tables max, so there are polenty of them there, but you are creating an administrative nightmare on top of th one you already have.

Just specify the full number you want under HLCL and make sure DID is N

--
Fletch
Avaya E9-1-1 Product Manager
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top