Star Codes
azrobert:
I copied your Star Code into my OBi200 and it worked.
I get silence for a second then Dial tone.
What is your Phone Port's Primary Line DigitMap?
If it contains a rule that matches *91 remove it.
Did you see my previous post before I removed it?
I tried your Star Code on an OBi110 and got a Busy.
I didn't have time to investigate, so I deleted my post.
Apparently, that is not a valid command for an OBi110.
You said:
Quote
The Line DigitMap is empty.
Is the Line Port your Primary Line and its DigitMap empty?
Shale:
"What is your Phone Port's Primary Line DigitMap?"
Physical Interfaces > Phone 1 =SP1 Service
Voice Service > SP1 Service does not have a DigitMap
ITSP Profile A > DigitMap = (1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
So I am suspecting you are saying that I should get rid of the |[^*#]@@. part.
"Did you see my previous post before I removed it?" Yes, but after searching out one of the items, I did not remember accurately what the other one was, I think.
"Is the Line Port your Primary Line and its DigitMap empty? "
I think that is the Physical Interfaces > Phone 1 =SP1 Service thing. (I was using phone 1)
Physical Interfaces > Phone 2 =SP3 Service, and I guess I would modify the ITSP Profile C > DigitMap to be able to the *91 with phone 2 also.
Am I looking at the right places?
azrobert:
I thought about this and what I'm suggesting is not valid.
I'm correct that *91 must not match a rule in the Phone Port DigitMap or the Primary Line's Digitmap, but if it does you won't get a BUSY.
You will get an IVR message saying you have a configuration error.
[^*#]@@. will not match *91
[^*#] means the first character can be anything but * or #
I don't see the problem with your configuration.
It looks like your OBi202 just doesn't like your Star Code.
What firmware level is your OBi202?
My OBi200 is at Build 4477.
Try adding *91| to the beginning of your Phone Port DigitMap.
Do you now get the IVR message after dialing *91
Shale:
ModelName OBi202
HardwareVersion 1.3
SoftwareVersion 3.0.1 (Build: 4041)
I know this is not the latest software.
Adding "*91| " ---
Phone 1 port digit map:
Before (992xxxxxxxxxx|9921xxxxxxxxxx|[1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
Did in local interface:
After (also removed the 992 test from before)
(*91|[1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)|**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))
After the change, I got SIT tones, and "there is no call route available to complete your call"
azrobert:
This proves that your previous configuration didn't have a stray rule somewhere that matches *91.
The only thing I can suggest is upgrading your firmware. If you don't want to upgrade because you want to use the old method of adding GV, I think Build 4350 is the last build to support the GV old method. This is from memory and my memory sucks, so you better confirm that build 4350 supports the GV old method.
Navigation
[0] Message Index
[*] Previous page