Automating CLI change on Line failover

<< < (2/2)

ianobi:
I will think about the main problem over the weekend, but I’m not hopeful!

Back to this <9:9>

If you dial 9021234567, then this rule in Msp2 9<0:72>[2-489]xxxxxxx will change the number to 97221234567. That’s fine.

When the number is processed through Phone Port OCR then this rule <9:9> will take the first 9 and replace it with 9, so the number remains as 97221234567.

If you look at call history and try with the <9:9> rule and without it, I don’t think you will see a difference.

I think my brain is now over heating. I will look again tomorrow  8)

ianobi:
Mrjoe,

I apologise for my last post  :-[ You are being too clever for my brain to cope with  :)  Let me see if I now understand:

If you dial 9021234567, then this rule in Msp2 9<0:72>[2-489]xxxxxxx will change the number to 97221234567.

In the Phone Port OCR you are using the <9:9> as a method of selecting numbers starting with 9 that fit Msp2.

Then this rule:

{(<9:9>(Msp2)):sp2(02xxxxxx>)}

resolves to this:

{(97221234567):sp2(02xxxxxx>97221234567)}

where 02xxxxxx is a spoofed number that looks like your caller id. It is a literal number and you are using the xxxxxx simply to keep your spoofed cid private on this forum.

Am I close?

I know you came here for help, but I think it may be me that needs your help on this one  :)

mrjoe:
Thanks Ianobi,
Exactly,
But I use it more like one would use 9 to get an outside line on a PBX System.
When I want to dial Israel showing my Home no. as caller ID, I dial 9 hear a new dial tone and then I dial national 02/03/04 etc.

mrjoe:
I shouldn't have used Xs in such a forum in place of Digits, especially not within a dial plan example.  :-[
I'm going to change it now.

Navigation

[0] Message Index

[*] Previous page