Call Centric w/ multiple SIP devices connected?
azrobert:
When this problem occurs again, check in Callcentric if the clients are registered. On main page under Extensions it shows the number of extensions defined and how many are registered. The clients might think they are still registered, but aren't.
Did you manually configure Callcentric or did the OBi auto-configure the trunk? If you manually configured, CC recommends keep-alive.
http://www.callcentric.com/support/device/obihai/obi202
Taoman:
Quote from: Ember1205 on November 05, 2016, 09:57:35 am
The Call Treatment "rings" two extensions. One is the Obi and the other is the ZOIPER client. There is no "forward to iPhone".
Right. Wrong terminology. I meant ring your Zoiper extension.
Quote from: Ember1205
The CC message playing was almost certainly the result of my having the ring interval set to short since I had it at 20 seconds. Calling the GV number didn't send you immediately to the CC message - it took about - yep, you guessed it - 20 seconds (even when ZOIPER wasn't ringing).
And even though it rang for 20 seconds your OBi didn't ring at all? What does your CC call records show? Is the call being routed to the correct extensions as expected?
Quote from: Ember1205
I do not see a way to change the ZOIPER client to TCP as that setting is grayed out with UDP selected.
Unfortunately I don't use Zoiper so I can't be much help. Perhaps deleting the config and starting over would allow you to choose TCP? Found some posts saying when Zoiper was configured using UDP on an iPhone and wasn't the "active" app it would "sleep" and not respond to SIP packets. Changing to TCP apparently allows iOS to "take over the TCP connection."
Quote
When using TCP, Zoiper will hibernate and iOS will take over the TCP connection, will reply to TCP keep alives and will not wake up the application unless a SIP message is sent to zoiper.
http://community.zoiper.com/238/zoiper-work-background-shown-background-screen-clocks-better
Ember1205:
I see no way to change from UDP to TCP in the app.
I see all of the "missed" calls in CC, and digging deeper into logs and such, they actually DID reach the house (Obi device). So, it appears that my issues are actually:
- ZOIPER won't keep the connection alive in the background on an iOS device and I can find no way to switch to TCP
- I had the ring duration set wrong in the Call Treatments which was resulting in getting a message from CC instead of ending up in the GV voicemail system
Ember1205:
One question still...
I believe the CC setup was done via the portal with little input from me (credentials). How do I check the keepalive setting? All I can find is something called KeepAliveInterval which is set to "0" (disabled?).
Ember1205:
I tried Linphone and was able to switch to either TCP or TLS - both resulted in the SIP client not being able to connect. ZOIPER might be blocking access to the TCP setting because it maybe doesn't work with CC?
Navigation
[0] Message Index
[#] Next page
[*] Previous page