Can the # symbol be used in call routing?

[AaronPearl]

We are trying to find a way of eliminating conflicts in the call routing table,( example: We have 55 set as intercom, but are now unable to dial area code 559) is it possible to use the # symbol in call routing?

[KSComs]

AaronPearl, if you nned paging and also 559 for dialling a prefix why not just use 155 for paging if 155 does not interfere with any other routing.

Kevin

[AaronPearl]

Normally this wouldn't be such a big issue. But the customer insisted on keeping old 3 digit extensions ( all in the 100 - 199 range) and is very picky about what they dial for intercom. Just wanted to know if there was a way to keep the 55 for intercom and still be able to dial 559 for area code.

[KSComs]

Normally this wouldn't be such a big issue. But the customer insisted on keeping old 3 digit extensions ( all in the 100 - 199 range) and is very picky about what they dial for intercom. Just wanted to know if there was a way to keep the 55 for intercom and still be able to dial 559 for area code.


is 555 out of the question ?

[AaronPearl]

555 is used to dial information in another state here in the US. What's happening is when the customer dials 55 they activate the intercom feature. Whet the dial 559 as an area code they activate the intercom and then are told "that number does not exist". I am thinking that maybe its just the order of the rules in the rule table or maybe there is a way to tell the epygi how to distinguish between the two in the rule table.

[davrays]

There should not be such problem if you configure the rules correct... Can you list here those two rules as you have them in the CRT (patterns, NDS, filters.. everything else)?