number translate issue during ESS&LSP mode

[adel3]

Hi Fisher ,


you are right ,so i think from the IGAR we can do it with the ARS for the LSP location

this link have one senario like you have :
http://198.152.212.23/css/P8/documents/100081291

Best Regards,
M. Adel

[yu63]

Hi Fisher

you can configure it from the ARS and the route pattern , just you shoud put in the ARS the pattern you want to convert from external to internal as the following:

Dialed String >>>012345xxxx


Total Min Max >>>> 9-10

Route Pattern = 100


since xxxx is the last 4 digits of your extension number you want to dial internal .

then go to the rouut pattern 100 to put your conversion

No. of Deleted Dgts = 6

Inserted digits = 2

this is if your extension 2xxxx


Best Regards,
M. Adel

Hi Adel,

Thank you for the input.

I think I still need to separate the full public number of LDN from the router pattern, since it cannot be converted to internal extension number in both normal work mode or ESS model. Am I right?

kind regards
Fisher

[adel3]

Hi Fisher

you can configure it from the ARS and the route pattern , just you shoud put in the ARS the pattern you want to convert from external to internal as the following:

Dialed String >>>012345xxxx


Total Min Max >>>> 9-10

Route Pattern = 100


since xxxx is the last 4 digits of your extension number you want to dial internal .

then go to the rouut pattern 100 to put your conversion

No. of Deleted Dgts = 6

Inserted digits = 2

this is if your extension 2xxxx


Best Regards,
M. Adel

[yu63]

You need to look at Dial plan transparency , this feature will work well for you see link.

http://www.avaya.com/master-usa/en-u...s/dpt-igar.pdf

Hi Richa,

Thank you for the sharing.

For my case, I think there will be more configuration in the "ars digit-conversion".
One thing: translate the PSTN number of far-end users to internal extension number (save money);
the other thing: in the same list, keep the LDN PSTN number still goes through ARS, not translate to internal extension number.

I don't test it in real environment yet, but I will try.

thanks angain!

kind regards
Fisher

[richa164]

You need to look at Dial plan transparency , this feature will work well for you see link.

http://www.avaya.com/master-usa/en-us/resource/assets/applicationnotes/dpt-igar.pdf

[yu63]

Hi Guys,

I am wondering whether you have experience on this.

The scenario:
CM V6.2 with remote site deployment, when one site user dial the other site user's E.164 number, we can translate the E.164 to extension number to avoid the long distance call charge.

When the remote site disconnected with other site, and work on ESS/LSP mode. Other site users dial his E.164 number and the call will be changed to internal call (translated to ext), then the caller will hear busy tone. It also apply when the ESS users dial other sites' E.164 number.

Any idea?

I believe IGAR will not work in this scenario.

thanks in advance!
Fisher