setting my outboundcallroute config to block outgoing calls while retaining e911
DirtAddsHP:
To answer qigcass question about what port my POTS line goes into my obi.. it goes into the phone port not the line port.
Hello ianobi,
I tried the change you made and it appears to work! Thank you, to answer your question i block calls out to comcast as someone in my house keeps abusing their service trying to make changes the account. We have taken that said person off the authorized account holder list but to block the number also helps.
I am comparing the change you made compared to my old attempted config.. looks like you put,{([1-9]x?*(Mpli)):pp}, after the forced 933 and 911 calls out the SP2 interface. and took out the |911):li} Is this correct? I would like to know what i did wrong here.
Oh and i meant digit map, not dial map.. wrong word.
ianobi:
Quote
To answer qigcass question about what port my POTS line goes into my obi.. it goes into the phone port not the line port.
This is worrying! If the PSTN line is still physically connected to your home phone wiring, then the POTS line should be connected to the OBi Line Port. If you know that the PSTN line is physically disconnected from your home phone wiring, then you may connect the existing house wiring to the OBi phone port to connect your house phones to the OBi.
My suggested OutboundCallRoute was based on your new one which works. I simply added {(18002662278|18009346489):}, to the front. I also left out {(MComcast):} If {(MComcast):} is only one number, then you may as well add it to the first rule - {(18002662278|18009346489|12345678901):}
I removed |911):li to make sure that there was no possibility of 911 going to the Line Port.
In any OutboundCallRoute or InboundCallRoute the rules are processed from left to right. The first rule that matches is used. This is not true in DigitMaps, but that’s another subject altogether.
It’s difficult to give a complete answer to your problems without all the details of your whole configuration. For instance, I wonder if 933 has been added to your Phone Port DigitMap. It should look like this:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|933|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
The general rules are that DigitMaps “allow” which digits/number formats may be dialled, InboundCallRoutes and OutboundCallRoutes route complete numbers to the correct destinations. (That’s a little simplified, but a good start).
I hope that you are now up and running as you want to be.
DirtAddsHP:
Hello ianobi,
I may be using the wrong terminology, when i say POTS i mean the wiring inside the house. We do not have copper telephone lines coming from the telecom company into our house. Only internet based phone though an ISP or in my case using the OBi and Google Voice / Callcentric. Our internal RJ-11 type phone jacks are daisy chained in our house, that is what the phone port on the OBi is connected to. Not to a phone company outside of our house.
Ah i see, maybe that {(MComcast):} entry is messed things up, i have two numbers defined in my User defined digit maps. And no i do not have 933 as a digit map entry, though it appears 933 works with the config you sent me. Is there any reason i should add it as a User Defined Digit Map?
Under Physical Interfaces > PHONE Port > DigitMap: here is my config
{pli:(xx.)},{sp1:(<**1>xx.)},{sp2:(<**2>xx.)},{li:(<**8>xx.)},{pp:(<**9>xx.)}
thank you for all your help ianobi and giqcass.
ianobi:
Looks like your phone wiring is OK.
I recommend starting with the following config, then we can fine tune if required:
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|933|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))
Physical Interfaces > PHONE Port > OutboundCallRoute:
{(18002662278|18009346489):},{17771234567:sp2},{911:sp2},{933:sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
DirtAddsHP:
Hello ianobi,
Question, How will modifying the DigitMap help me? Everything seems to be working fine now.
Navigation
[0] Message Index
[#] Next page
[*] Previous page