There needs to be a better way
Rick:
There are numerous ways to configure the OBiTalk. I assumed, apparently incorrectly, that a new user should use OBiTalk. I did that with GV and it worked great. I tried to do that with CallCentric for SP2, and it did NOT work great. I receive calls, but cannot make calls. CallCentric is currently reviewing my data and I hope for a quick fix and then a 911 test.
The point of this post is that I can't find any SIMPLE and CLEAR explanation of the reasons to use one configuration method over another. I think I read that if I use the direct config via IP, then ObiTalk will overwrite it.
Can someone clearly explain this for myself and other new users?
Thank you.
RonR:
Configuring the OBi directly/manually is not complex. If all you need is a simple cofiguration with a Google Voice account and nothing more, it's probably a push as to whether the OBiTALK Web Portal is quicker and easier. If you need anything more, I feel it's much simpler and faster to access the OBi directly. Plus you have much more control and status information available if you acess the OBi directly.
By default, Auto Provisioning is enabled in the OBi, allowing the OBiTALK Web Portal to take control of configuring the OBi. If you elect to configure the OBi directly, you must disable Auto Provisioning in order to prevent the OBiTALK Web Portal from having its way:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Manually configuring Google Voice on SP1 is very easy:
Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
Manually configuring a SIP provider such as Callcentric on SP2 is no harder:
Service Providers -> ITSP Profile B -> General -> Name : (provider name)
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : (proxy server)
Service Providers -> ITSP Profile B -> SIP -> OutboundProxy : (proxy server) (if an outbound proxy is used)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> AuthUserName : (sip username)
Voice Services -> SP2 Service -> AuthPassword : (sip password)
Voice Services -> SP2 Service -> CallerIDName : (callerid name)
Rick:
Ron:
Thank you, that makes it clearer.
So, after one sets up SP1 and SP2, is the digimap created or does one have to do that also? I'm still working understanding the digimap syntax.
Then, once I have the two services setup, I have to put in 911 to the CallCentric digimap... :)
RonR:
Quote from: Rick on December 29, 2011, 01:06:33 pm
So, after one sets up SP1 and SP2, is the digimap created or does one have to do that also? I'm still working understanding the digimap syntax.
Most settings in the OBi have a factory default value that is usually a reasonable starting point.
The default DigitMaps in the OBi will get you going, but you will probably want to enhance them at some point. For example, you might want 7-digit local dialing capability, in which case you could use the following on SP1 and SP2:
Service Providers -> ITSP Profile A/B -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)
where aaa is your local area code.
DigitMaps and OutboundCallRoutes are probably the most difficult aspect to get your head around. Download the OBi Administrator Guide and spend some time studying it if you want to get proficient into this area.
Quote from: Rick on December 29, 2011, 01:06:33 pm
Then, once I have the two services setup, I have to put in 911 to the CallCentric digimap... :)
Normally, 911 calls are routed to the LINE Port by a rule in the PHONE Port OutboundCallRoute:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
To send 911 to SP2 instead, it's a minor change:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Rick:
Quote from: RonR on December 29, 2011, 01:23:24 pm
Quote from: Rick on December 29, 2011, 01:06:33 pm
So, after one sets up SP1 and SP2, is the digimap created or does one have to do that also? I'm still working understanding the digimap syntax.
Most settings in the OBi have a factory default value that is usually a reasonable starting point.
The default DigitMaps in the OBi will get you going, but you will probably want to enhance them at some point. For example, you might want 7-digit local dialing capability, in which case you could use the following on SP1 and SP2:
Service Providers -> ITSP Profile A/B -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>[2-9]xxxxxx|011xx.|(Mipd)|[^*#]@@.'@'@@.)
where aaa is your local area code.
DigitMaps and OutboundCallRoutes are probably the most difficult aspect to get your head around. Download the OBi Administrator Guide and spend some time studying it if you want to get proficient into this area.
Quote from: Rick on December 29, 2011, 01:06:33 pm
Then, once I have the two services setup, I have to put in 911 to the CallCentric digimap... :)
Normally, 911 calls are routed to the LINE Port by a rule in the PHONE Port OutboundCallRoute:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
To send 911 to SP2 instead, it's a minor change:
Physical Interfaces -> PHONE Port -> OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{(<#:>):li},{911:sp2},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},
{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
Ron:
I appreciate your help. For many years I provided help on the Dell forums, racking up over 30,000 posts :). Helping others learn is what it's all about.
I downloaded the guide the other day, haven't gotten into it yet. I had planned on doing this last week, after switching my alarm to cellular and porting my landline, but that went awry and I'm now putting an internet module on the alarm and then beginning the porting late tomorrow or Saturday.
Here's what CallCentric told me to put in for SP2:
(*xx.|**275*x.|[3469]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Doesn't look anything like the one you suggested, at least to me. :)
Navigation
[0] Message Index
[#] Next page