Two PhonePower Accounts - One Obi202 Device - Register Failed
MikePA:
I could not get PhonePower to work on SP2. Had to implement on SP1 and put Anveo on SP2.
drgeoff:
Quote from: MikePA on May 03, 2014, 05:08:09 pm
I could not get PhonePower to work on SP2. Had to implement on SP1 and put Anveo on SP2.
"could not get to work PhonePower to work on SP2" by which of:
1. The OBi Dashboard
and/or
2. Expert Configuration at obitalk.com
and/or
3. Configuration by device's local web server?
dwhitejazz:
Obihai has resolved the issue with configuring two PhonePower accounts on a single Obi202 device.
Obihai did not issue a firmware update, therefore the fix was only in their provisioning script and the parameters.
One thing I noticed: even though both SP1 and SP2 are "Registered" and work, when I edit the configuration the VOIP Phone Number (xxxxxxxxxx@sip.phonepower.com) setting (in basic mode, not expert) is blank, yet the configuration works.
I recommend doing a factory reset of the Obi202 device, deleting the device from the ObiTalk portal, and then re-adding it. Then resync your PhonePower accounts. You will save yourself a a lot of headaches. You must also disable SIP-ALG on your router, and use the correct port-forwarding settings (or put the Obi202 device in the DMZ zone). If anyone wants the list of ports I can post them here.
Finally, even though both my PhonePower accounts are configured and working, there is obvious latency when calls are forwarded through GoogleVoice. The latency when going through PhonePower directly (outgoing or incoming calls) is minimal and not noticeable. Therefore, we may be porting our GoogleVoice numbers over to PhonePower since most of the services GoogleVoice provides are available there.
dwhitejazz:
I'm still waiting for Obihai to tell me exactly what they changed in order to get the 2 PhonePower accounts working on a single Obi202 device.
I want to know the exact list of parameters, and if anything outside of the parameters had to be fixed.
I do know that no firmware update was needed to resolve the issue.
dwhitejazz:
From Obihai: Minor (but irritating) bug. SIP service settings were assigned to the incorrect service slot in the OBi.
No details yet regarding which specific parameters needed to be fixed, but that was the issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page