Callcentric-Obi202 setting's
cici235:
I followed CallCentric's instructions on changing the ITSP Provisioning to disabled. If I a have a second extension should I also perform the same steps under ITSP B General for my extension set up on SP2 (177784XXXXX101)?
CallCentric's instructions also tell me to disable OBiTALK Provisionings parameter name to "Disabled"
Looking throughout the Obi202 expert setup page I am unable to find this option anywhere? Am I missing something?
This is what my provisioning set up looks like.
drgeoff:
Disabling Obitalk Provisioning is only applicable (and available) if you are configuring your OBi using its onboard web GUI via its local IP address. 'Disabled' prevents the portal (basic or expert modes) from configuring the OBi. That is why the setting is not present on the portal.
The name field in your screenshot is merely for information/cosmetic purposes. You can put what you like in there but your proposed '1777.....101' is fine.
To configure SP2 for the 101 extension click on Voice Services, then SP2 Service. Scroll down to SIP Credentials. In the AuthUserName and AuthPassword fields enter what you have used for the 101 extension on the CC web site.
cici235:
I am currently using Anveo and find the call flow very difficult to figure out.
My problem is I hate to experiment with my working phone system. I decided to buy an extra obi202 and try other providers. So far I have found CallCentrics system a little easy to work through. The call treatments are not doing what I would like but I have only spent a short time playing with the settings.
I have been able to set up SP1 and SP2 showing both as registered. I get the same confirmation from CallCentric showing the welcome message “YOUR PHONE IS REGISTERED” for both extensions. The system seems to be working properly and both lines ring out and can be answered as one would expect. It’s what happens while both lines are in use that I'm struggling with (busy signal, or message Etc.).
In your opinion does it sound like I'm ready to devote my time to the CallCentrics system and there call treatments?
Thank you so much for your help. Looking forward to never having to go back to AT&T and their $214.00 phone bill (two lines and that didn't include internet).
SteveInWA:
It seems to me that you are creating unnecessary complexity and getting in over your head, by disabling the portal provisioning and getting into manual expert mode. There is no need to do this at all.
Ignore Callcentric's setup guide. If you have previously added the OBi to your OBiTALK portal dashboard, then log into the portal, and delete the OBi. Pull the power cord and the Ethernet cord. Plug in just the power cord and let it boot up. Pick up the phone and key in ***8 and then 1 to restore it to factory defaults. Pull the power cord and plug in the Ethernet cord, and then the power cord and let it reboot.
Now, you have a "virgin" OBi, ready to be added to the OBiTALK portal. On the Portal, follow the "add device" procedure, keying in **5 etc. Once the device is added, OBiTALK will walk you through configuration. It will display a page of service providers (Google Voice, PhonePower, etc.). Scroll all the way down to the bottom of the web page and select "OBiTALK Compatible Service Providers". On the next page, click the Callcentric link. This will load correct, preconfigured settings for Callcentric. All you need to do on the next page is enter your Callcentric SIP credentials, and it will simply work, with less than 10 minutes of effort, to configure both SP1 and SP2 for your Callcentric DIDs.
cici235:
Once again thank you for your expert advice.
Simple is what I looking for. This way if the Obi202 device ever fails it won't be a major undertaking to replace the hardware and make the required changes.
Should I consider testing any of the other Service provider's? Phonepower?
My needs are simple. A busy signal when a both extensions are in use. Caller waiting turned off and automatic failover to a cell phone in the event of hardware or internet failure?
Anveo
Asterisk Compatible System
Broadvox
Callcentric
Engin
flowroute
freephoneline
Google Voice
InPhonex
ippi
Localphone
OneSuite
Phonepower
RealCalls
RingCentral
Telecube
Twilio
Vitelity
voip.ms
VoIP2Go
VOIPo
Navigation
[0] Message Index
[#] Next page