| |||||||||
 |
| ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: dial, rules, translation |
 |
| | LinkBack | Thread Tools | Display Modes |
 04-22-2006, 08:18 AM | #1 (permalink) | ||||||||
| Junior Member
Rep Power: 0  Country:  | Dial translation rules? I'm not exactly sure what I am looking for here ...  Years ago, when I administered a BTex 601 system (distant ancestor of the Meridian), we had a remote office and I set up short dialling codes to the remote office using a speed call list on the 601: this meant you could dial 74xx and it would forward to 901yyyyyy4xx. I would like to do something similar with the two Meridians we now have (one here, one in the remote office), but would like to avoid the pain of programming 1,100 speed call lists (2xxx at remote office, 4xx at local office).... Is there a way I can set up some sort of translation pattern, so that when a user dials 4xx it translates this to 901yyyyyy4xx? We do not have a trunk linking the two sites; VoIP was looked at but dismissed on grounds of cost  . It would be a bonus if these numbers appeared 'local' to each Meridian, but that's not necessary. Basically I want a user to be able to dial an extension number from either site and have it route through transparently as if they were local extensions. I do not (yet) have the option of a trunk, and it's unlikely one would be implemented as the plan is to phase out the Meridian and replace it with a Cisco Call Manager system...So:
And having read on how speed call lists work with the Meridian it seems you need to dial an FFC to use them ... so I couldn't make them work in this transparent fashion like I did with the old crufty BTex 601.... Bonus: is there a way to also set this up so that each office sees the caller ID of the calling extenstion going either way, rather than the main switchboard number? Thanks (goes off looking for this 'Introductions' forum again ... ) | ||||||||
 |   |
| 04-22-2006, 11:34 AM | #2 (permalink) | ||||||||
| Senior Member   slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 Gender:  Country:  | Sounds like Distant Steering Codes (CDP) might do the trick for ya provided that none of those number ranges you want to translate conflict with numbers that are already on the system. For example - (there is a bit more to it than this) At the local office 4 would be programed as a DSC, the DSC would point to an RLI that uses a DMI to insert the correct digits and then send it to a trunk group (I'm assuming PSTN) that the calls would take had they been dialed normally. Same basic idea at the remote but this time it would be using 2. You could probably also accomplish the same thing with a pretanslation table - basically 1 speed call list that would automatically insert the correct digits in front of any dialed number leading with a 4 at the local and 2 at the remote. | ||||||||
| | |
| 04-22-2006, 12:55 PM | #3 (permalink) | |||||||||
| Junior Member  anil has no status.
Location: kuwait Rep Power: 7 Gender:  Country:    | Quote:
you can also translate extensions | |||||||||
| | |
| 05-01-2006, 10:39 AM | #4 (permalink) | |||||||||
| Junior Member
Rep Power: 0 Country: | OK I implemented this using a DSC and a new RLI as you said, Slagburn. However, it doesn't quite work Since I implemented it, calls to the remote office are occasionally going 'silent' - i.e. I call, I can hear the remote party, but they can't hear me. It seems to work fine if the remote DDI number is used, but if I use the DSC I set up it seems to not be clearing properly somewhere. I.e. Dial 481 ... call is OK ... hang up Dial 481 again ... called party can't hear me ... hang up Dial 481 again ... call is OK ... hang up Dial 901xxxyyy481 ... called party can't hear me ... hang up. (PS Doesn't have to be the same number called ... Happens if you dial extensions with little time between calls... the problem seems to be related to clearing the call?) I created a new DMI, numbered it '24' and told it to remove 0 digits and to insert '01xxxyyy'. Then I created a new RLB which is a copy of the existing outgoing trunk's RLB but is told to use DMI 24. Not sure what the problem could be. The config is below. -M. OVL000 Quote:
 Last edited by Velouria; 05-01-2006 at 10:45 AM. | |||||||||
| | |
| 05-01-2006, 10:48 AM | #5 (permalink) | |||||||||
| Senior Member slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 Gender: Country: | Quote:
| |||||||||
| | |
| 05-01-2006, 12:31 PM | #6 (permalink) | |||||||||
| Junior Member
Rep Power: 0 Country: | Quote:
Got the time now - but no one else at the other end to answer the phone! One question is ... what's the difference between an LSC, a DSC and a TSC? (I realise that would probably be covered in Meridian training, if I'd had any!) | |||||||||
| | |
| 05-01-2006, 03:06 PM | #7 (permalink) | ||||||||
| Senior Member slagburn has no status.
Location: 3498.51 miles from Tiverton, Ontario (CANADA) Rep Power: 16 Gender: Country: | LSC is for steering calls locally on the switch - I don't think it gives an RLI option with those. DSC and TSC (trunk steering codes) are simliar but TSCs are a lot less flexible if memory serves me right. If I find my NARS / BARS book I'll expound with a little more detail. | ||||||||
| | |
| 05-06-2006, 09:00 AM | #8 (permalink) | ||||||||
| Junior Member
Rep Power: 0 Country: | Just to update you .... got it all working. The silent calls thing is a mystery. BT engineers checked both ends and couldn't find any fault. I'd set the thing up flawlessly (thanks to you lot ).Can't get the same thing to work in reverse from the other end but I think that's cause numbers starting with 2 are not in the dialling plan at the other site for customer 0. Got it to work as a 5xxx DSC (by getting the DMI to DEL 1 digit and INST 01xxxyy2) and will revisit why it doesn't work as 2xxx next week... Yeah slagburn ... the BT engineer said that, for what I was doing DSC/LSC/TSC were all functionally equivalent but each can do things the predecessor can't (in ascending order) and *technically* I should set it up as a TSC but it doesn't make any real difference Next step is to add another remote office as 6xx and then add them to the Cisco VOIP system (just create dial-peers in the gateway for 4xx and 6xx, pointing from Cisco to Meridian, and put them in the dialling plan - should be relatively easy). edit: one of the reasons for doing this is there are plans to implement VoIP trunks - once that's done all I would have to do is change the trunk the DSC points to, since it's already in existence. Last edited by Velouria; 05-06-2006 at 09:06 AM. | ||||||||
| | |
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
 Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Changing the number a set is forwarded to from off site. | pcutler | Meridian Systems | 7 | 11-28-2007 11:56 AM |
| I/C DID to CFW to COT fails | jshaw | Meridian Systems | 7 | 09-07-2004 11:34 AM |
| Say what? | Sherrill | Off Topic - Humor/Jokes | 2 | 03-07-2003 12:15 PM |
| dial modes in telephones | mgracian1971 | BCM and Norstar | 2 | 12-27-2002 02:34 PM |
Linear Mode
