News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi 100 and Callcentric CNAM

Started by Mark55, March 02, 2013, 08:45:17 AM

Previous topic - Next topic

zapattack

Call Status is displayed during a call on the Obi by using web access to the Obi, not the Obi Dashboard, and checking under the first heading: Status. After completion, partial info will remain in Call History.
You must click Call Status after the call has started, not before.

Mark55

Quote from: zapattack on March 09, 2013, 06:39:13 PM
Call Status is displayed during a call on the Obi by using web access to the Obi, not the Obi Dashboard, and checking under the first heading: Status. After completion, partial info will remain in Call History.
You must click Call Status after the call has started, not before.

Thanks for clarifying that, zapattack. Thats why I couldnt find it before - was looking in the Dashboard.

Mark55

Logged into the Obi 100 via the IP addy. Made the necessary configuration changes as described in the instructions. Outgoing calls are going through GV on SP1. Incoming calls do not even register with the Obi, however. Incoming is supposed to go through CC on SP2, and yes, the instructions were followed to the letter. When the configuration changes are made to allow this, the Obi doesnt even ring. (The CNAM info does show up on the CC Dashboard, though.)

Also, even when using the IP addy to make the changes, the configuration changes do not stay there. Come back to that page in a few minutes, and they have reverted back to their defaults. And yes, they were saved - all of them - and the unit was rebooted with each change. Something is wrong....

CoalMinerRetired

Quote from: Mark55 on March 04, 2013, 08:03:35 AM

- I used the ObiTalk Portal to make the configuration changes, in Expert Configuration mode.


Quote from: Mark55 on March 14, 2013, 02:32:22 PM
Logged into the Obi 100 via the IP addy. Made the necessary configuration changes as described in the instructions.

.... the configuration changes do not stay there. Come back to that page in a few minutes, and they have reverted back to their defaults. And yes, they were saved - all of them - and the unit was rebooted with each change.

Something is wrong....

You make changes via one method only, ObiTalk Portal or IP addy. See this: Managing Your OBi Device Configuration: OBiTALK or OBi Web Page but NOT Both.

When you use the ObiTalk Portal method to configure, you can look at things via IP Addy, but as you found out you cannot edit.

Mark55

I know that!! Since the website didnt seem to work, it was suggested to try it through the IP and see what happened. Now the website (Obitalk) in expert mode will save the configuration changes, yet when they are applied the Obi is cut totally out of the loop, out of the call path for incoming calls, and the phone does not even ring. Hence there are NOTHING in the call history nor on Active Calls when this happens. The CNAM does show up on the CC Dashboard.

I have run this at least at a dozen time, perhaps more, and get the same results each time. Perhaps its time to reset it back to its factory specs and start all over.

Mark55

Problem solved. From CC support:

"As you have mentioned that you are using a Netgear router, please log onto your router's configurations, and locate any setting pertaining to 'Stateful Packet Inspection (SPI)' (SIP ALG); generally this setting would be under the WAN setup page (Advanced), if you are able to locate that setting, please ensure that this setting is disabled as it may cause potential issues with VoIP."

That did the trick and now its working great.