Set up Obi110 with Google Voice as Service Provider 1. Worked first time; works perfectly.
Trying to set up Sipgate as Service Provider 2 (for incoming calls).
Continuing error is "Register failed: no response from server. (server=204.155.28.10:5060; retrying)"
I have set:
Voice Services -> SP2 Service -> X_ServProvProfile : B
SIP Provider 2:
Service Providers -> ITSP Profile B -> General -> Name : (SIP Provider 2 Name)
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : (SIP Provider 2 Proxy Server Hostname)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> AuthUserName : (SIP Provider 2 username -- the 1234567a0 one)
Voice Services -> SP2 Servier -> AuthPassword : (SIP Provider 2 password -- the AB1CDE one)
Voice Services -> SP2 Service -> CallerIDName : (SIP Provider 2 CallerID)
Physical Interfaces -> PHONE Port -> PrimaryLine : (SP1 Service or SP2 Service)
I have also enabled STUN and have tried STUN port 10000 and 3478
Is there something I'm missing? Anything else I might try?
Starting with all settings on SP2/ITSP B at Default, these are the only settings required to register and make/receive calls with Sipgate:
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : sipgate.com
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> AuthUserName : (sip username)
Voice Services -> SP2 Service -> AuthPassword : (sip password)
A STUN server is a good addition. I use:
Service Providers -> ITSP Profile B -> General -> STUNEnable : (checked)
Service Providers -> ITSP Profile B -> General -> STUNServer : stun.ideasip.com
Service Providers -> ITSP Profile B -> General -> X_STUNServerPort : (Default)
My Sipgate account works perfectly with these settings.
If you're still having difficulty getting Sipgate to register, temporarily bypass your router by connecting the OBi directly to the modem. Do this with both units powered off. After making the direct connection, power the modem up first and allow it to attain sync before powering up the OBi.
Hrmmmm... No problem doing that, but how will I know what the Obi is experiencing? I'll have no internet on a computer so no way to run Obitalk...
Quote from: SnerdlyBosco on January 14, 2012, 07:11:34 PM
No problem doing that, but how will I know what the Obi is experiencing? I'll have no internet on a computer so no way to run Obitalk...
The goal is to see if you can you make and receive calls using Sipgate without the router in the loop. If you can, then your router is probably the culprit. If not, the router is likely not the problem.
If Sipgate still fails, make sure you can still call the echo test at **9 222 222 222 while the OBi is connected directly to the modem.
Okay, I hooked the Obi110 directly to the DSL modem, bypassing the router. Waited for modem to sync up before turning Obi on. Waited for solid green phone light on Obi. Attached phone did not ring when Sipgate number called. Phone DID ring when GV number called. Call out DID succeed on GV service. Obi Echo test DID succeed.
But then it gets weird.
When I connected Obi back to router and logged into ObiTalk, the Service Provider 2 (SipGate) WAS registered.
I tried placing a call to the Sipgate number and got a stuttering ring on the phone (physical ring, not ringback). Attempted to answer, but only got dialtone (Google Voice's on SP1, I am assuming). The ringback tones in the calling phone continued.
Ever since that first call, ObiTalk shows "Register failed..." for SP2.
Would seem to verify that Sipgate credentials are correct and that the Obi is working. Any other ideas to troubleshoot? Does the stuttering ring suggest anything?
Quote from: SnerdlyBosco on January 15, 2012, 12:20:19 PM
When I connected Obi back to router and logged into ObiTalk, the Service Provider 2 (SipGate) WAS registered.
.
.
.
Ever since that first call, ObiTalk shows "Register failed..." for SP2.
Just keep in mind that the OBiTALK Web Portal is not always up-to-date and is not always accurate. The only things that really matter with an OBi are the configuration settings in the OBi itself and the status that the OBi itself is reporting. Relying on OBiTALK Web Portal settings and status when troubleshooting a problem can add confusion resulting in wrong conclusions.
Quote from: SnerdlyBosco on January 15, 2012, 12:20:19 PM
Does the stuttering ring suggest anything?
It suggests you have unread voicemail at Google Voice.
The stuttering ring I refer to is the physical ringer on the physical phone attached by wire to the Obi. When I placed the call to my Sipgate number, the physical ringer on the physical phone gave an incomplete ring. Where the phone's normal ring is two or more seconds per blast, when Sipgate made it ring, it was only one second and not ringing all the way through that second -- sort of "stuttering."
Does a flawed physical ring on an incoming Sipgate call indicate that I have unread Google Voicemail?
Do you have a different ring pattern set on SP2 compared to SP1?:
Voice Services -> SPx Service -> X_DefaultRing
The OBi generates the ring voltage and pattern for the PHONE Port, not the service provider.
Both SP1 and SP2 have Xdefaultring of "1".
Yet the incoming Sipgate ring and the incoming Google Voice ring are different. The Sipgate ring stuttered like the ringer had a bad electrical connection (that's what it sounded like, not what caused it).
Could it have been a call on the OBiTALK Service (check the Call History)? It uses a double-ring pattern that's different.
Quote from: SnerdlyBosco on January 15, 2012, 01:25:28 PM
Both SP1 and SP2 have Xdefaultring of "1".
Yet the incoming Sipgate ring and the incoming Google Voice ring are different.
Do they both have the same X_RingProfile (should normally be A)?
Stewart: SP1 has ring profile A, SP1 hs ring profile B. As far as I can tell, however, ring profile A and B are identical.
I'm not too worried about the stuttered physical ring -- just wondered if that symptom might help diagnose the problem.
Bigger issue seems to be that the line isn't registering.
Any further troubleshooting come to mind?
Ring profiles A and B (by default) are not the same. Compare Ring Pattern 1 for both; you'll see the A specifies 2 on, 4 off (normal US ring), while B is 0.4 on, 0.2 off, 0.4 on, 2 off.
As to the registration problem, please post modem make/model and router make/model, and any special setting in either.
Thanks, that ring pattern is probably what I heard. The cordless phone has its own ringtones that probably don't know what to do with a non-standard/short burst.
Modem is Embarq (carrier) EQ 660R ADSL
Router is Cisco/Linksys WRT610N V1, no special settings (that I recall)
And through all this Sipgate-not-registering thing, Google Voice continues to work flawlessly.
This morning, without changing any settings (all set as RonR suggests early in the thread), I pulled the power plug from the Obi and plugged it back in.
Then, I accessed setup from the unit's IP address (bypassing ObiTalk).
Sipgate (on SP2) registered. To test outgoing calls, I dialed **2 and my home number. It rang and connected upon answer. Result was one-way audio: receiving phone could hear the sending phone, but the sending phone could not hear the receiving phone.
Next, I tried a call to the Sipgate number. I received "you have reached a non-working number: announcement 14, switch 14-4152-1."
Curiouser and curiouser...
Quote from: SnerdlyBosco on January 16, 2012, 08:44:22 AM
To test outgoing calls, I dialed **2 and my home number. It rang and connected upon answer. Result was one-way audio: receiving phone could hear the sending phone, but the sending phone could not hear the receiving phone.
Next, I tried a call to the Sipgate number. I received "you have reached a non-working number: announcement 14, switch 14-4152-1."
These symptoms are often indicative of router issues. This might be a good time to revisit bypasssing your router and seeing if Sipgate works properly with the OBi connected directly to the modem.
Temporarily disable SP1/Google Voice:
Voice Services -> SP1 Service -> Enable : (unchecked)
and set the PrimaryLine to SP2 Service:
Physical Interfaces -> PHONE Port -> PrimaryLine : SP2 Service
This will allow you tell from the 3rd LED on the OBi whether you have registration on SP2/Sipgate.
Power both the modem and the OBi off. Make the direct connection. Power the modem on and give it plenty of time to attain sync. Then power the OBi on and give it plenty of time to attain registration with Sipgate (the 3rd LED should light).
First verify that you can reach the echo test at **9 222 222 222. Then try making and receiving calls with Sipgate.
RonR
Made the changes you suggested (Sp1 UNenable; primary line Sp2). Connected Obi to modem. Powered up as suggested.
Single green "phone" light. Solid.
Echo test successful.
Unsuccessful dialing out. Error was "The number you have dialed XXXX was rejected by your service provider. Reason was 488."
Unsuccessful dialing in. Call made from Google Voice gave ringback in receiver, but no ring on phone connected to Obi. Call made from landline gave no ringback in receiver and no ring on phone connected to Obi.
Re-checked Obi config upon reconnecting to router to confirm the above settings.
A 488 error is often a Codec problem. You haven't changed the Codec profiles in any way have you? My SP2 uses Codec Profile A.
In Voice Service > SP2 Service > X_CodecProfile is default set for "B"
Noting on that same page, AuthPassword is blank, with "device default" checked.
Quote from: SnerdlyBosco on January 16, 2012, 04:33:01 PM
In Voice Service > SP2 Service > X_CodecProfile is default set for "B"
You only need to set X_ServProvProfile to 'B'. X_RingProfile & X_CodecProfile can be left at 'A'. The Default on all these is 'A' on my OBi.
Quote from: SnerdlyBosco on January 16, 2012, 04:33:01 PM
Noting on that same page, AuthPassword is blank, with "device default" checked.
You need to put your Sipgate SIP credentials at AuthUserName & AuthPassword.
This morning, tried Obi connected direct to modem. SP1 UNenabled; SP2 as primary; SP2 Codecs set to "A."
Solid green light on phone indicator.
Placed call: rejected by service provider 488 (tried no area code, with area code and with leading 1)
Received call: no ringback tones in originating call handset; no ring on phone connected to Obi
Any further suggestions?
In the event I might have made a settings change that was masking (or causing) a problem, I factory-reset the Obi110 (paperclip and power on 'til green light flashed) and deleted service provider profiles from ObiTalk.
Then, to isolate SipGate (since Google Voice had been working flawlessly), I set up Sipgate on SP1, with nothing on SP2.
I ONLY did the minimal wizard setup, with NO changes in Expert config.
ObiTalk indicates "Service not configured." Connecting Obi direct to modem (bypassing router)
Solid green light for "phone"
Outbound calls get "(three tone) there is no service available to complete your call."
Suggestions as to where I might go from here?
Login to your Sipgate account and generate a NEW password. Use this new password and username on the OBi to see if you can get registration. If that doesn't work, contact OBi Support for more personalize support.
SnerdlyBosco,
If you didn't delete the OBi from the OBiTALK Web Portal Dashboard, resetting the OBi to factory defaults was a waste of time as the OBiTALK Web Portal immediately put everything back the way it was just seconds earlier.
Do the following:
1. Delete the OBi from the OBiTALK Web Portal Dashboard. Do NOT re-add it.
2. Reset the OBi to factory defaults by holding the reset button depressed for at least 30 seconds.
3. Log into the OBi directly and verrify that all settings have their Default checkbox checked.
3. Set nothing but the following:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Service Providers -> ITSP Profile A -> General -> STUNEnable (checked)
Service Providers -> ITSP Profile A -> General -> STUNServer : stun.ideasip.com
Service Providers -> ITSP Profile A -> SIP -> ProxyServer : sipgate.com
Voice Services -> SP1 Service -> AuthUserName : (sip username)
Voice Services -> SP1 Service -> AuthPassword : (sip password)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
4. Reboot.
5. Verify that all settings have their Default checkbox checked except for the settings defined above and that all of them are still correct.
6. Check the Main Status page and see if SP1 reports Registered. If so, attempt to make and receive calls.
SnerdlyBosco,
FWIW, I just performed the exact steps I outlined in the previous post.
The OBi immediately registered with Sipgate and I could successfully make and receive calls.
RonR
Ha! I was just coming back to tell you I'd taken some of your advice from elsewhere in the forum -- which is exactly what you've just posted here! Thanks for both...
Progress!
With ObiTalk disabled and the Obi provisioning disabled, Sipgate on SP1 registers fine.
I am able to place calls AND receive calls.
BUT, there is one-way audio on both placed and received calls. In neither case can the Obi-wired phone "hear." In both cases, the distant phone can hear.
Something in the router?
Thanks for getting me this far...
Quote from: SnerdlyBosco on January 18, 2012, 11:51:15 AM
Ha! I was just coming back to tell you I'd taken some of your advice from elsewhere in the forum -- which is exactly what you've just posted here! Thanks for both...
Progress!
With ObiTalk disabled and the Obi provisioning disabled, Sipgate on SP1 registers fine.
I am able to place calls AND receive calls.
I was confident you were getting all tangled up between the OBiTALK Web Portal, the OBiTALK Wizrd, and the OBi directly.
Do yourself a big favor and get familiar with configuring the OBi directly on your own. You'll end up thanking yourself in the end.
Quote from: SnerdlyBosco on January 18, 2012, 11:51:15 AM
BUT, there is one-way audio on both placed and received calls. In neither case can the Obi-wired phone "hear." In both cases, the distant phone can hear.
Something in the router?
That's most likely a router issue.
First call the echo test at **9 222 222 222 and see how that goes (it's usually more forgiving).
Then connect the OBi directly to your modem and see if bypassing the router solves the problem.
I suspect that the Embarq modem is configured as a router (since you were able to run the OBi with GV, when connected directly to the modem). You can confirm that by seeing whether the Linksys gets a public IP address on its WAN interface. If not, the modem is acting as a router and you have two NATs cascaded.
I don't know whether Sipgate requires NAT mapping -- try turning off STUNEnable. If that doesn't work, turn it back on and test with OBi direct to modem. If that also fails, you might put the modem in bridge mode and set up PPPoE on the Linksys. If the direct modem connection works, try forwarding the RTP port range across the Linksys.
Tried disabling STUN. One-way audio persists, with and without.
Connected Obi directly to modem.
Outbound call: SUCCESS! Both parties could hear.
Inbound call: FAILURE. Call placed with Verizon got "unable to complete your call" message. Call placed with Google Voice got ringback tones for caller, but phone connected to Obi did not ring.
I suspect that the Embarq modem is configured as a router (since you were able to run the OBi with GV, when connected directly to the modem). You can confirm that by seeing whether the Linksys gets a public IP address on its WAN interface. If not, the modem is acting as a router and you have two NATs cascaded.
I don't know how to see whether Linksys gets a public IP address on its WAN interface.
And one more step closer:
FINALLY found SIP-alg in my router (WRT610n, under Management | Advanced Features). Disabling that gave me two-way audio on PLACED calls from the phone attached to the Obi, through the router. Woo Hoo!
Still unable, however, to RECEIVE calls. Calls placed from Verizon still generate an error (You have reached a non-working number, most recently). Calls placed from Google Voice still generate ringback tones for the caller, but never ring the phone attached to the Obi.
Any further ideas?
Log into to your Sipgate account and put your mouse over the telephone icon where you can retrieve your SIP credentials. There is a 'Test phone' option on the menu that appears. Does clcking this ring the OBi and play the welcome message properly? If so, there may be a problem with your Sipgate DID.
Couldn't find the "test phone" option in Sipgate. Noticed that the telephone icon indicated "offline." I checked the Obi status and it was "unable to register, retrying in..."
Only thing I had changed was the SIP alg disable, so I enabled it and the Obi registered, the Sipgate.com phone icon indicated "online," and I was able to "test phone" successfully.
AFTER THAT, I was able to receive Sipgate calls to the Obi with two-way audio. Placing calls is back to one-way audio, but since all I need is incoming calls, I'm in good shape.
I might fuss with it again someday, but I'm going to try locking down the function(s) that I have and see if they'll persist.
Thanks for the help.
Quote from: SnerdlyBosco on January 18, 2012, 05:09:17 PM
Placing calls is back to one-way audio, but since all I need is incoming calls, I'm in good shape.
Forwarding ports 16600 - 16998 to the OBi might help with the audio issues. I always forward ports 5060 - 5061 also just to be safe.
Returning to the scene of the crime...
Obi will register with Sipgate, but I get one-way audio on BOTH placed and received calls. Phone connected to Obi does not hear on either, but distant party can hear what's being sent from the Obi.
Any recommendations? I feel as if I'm getting closer...
GV works flawlessly.
I have the same issues, spend quite some time on this. It seems the minute GV is included the SIP stuff gets affected. I have not tried configuring 2 different regular SIP accounts on the OBI and see if that works, but right now GV works and sipgate is registered, even rings, but when you try to pick up the call you cannot hear anything on the sipgate.
I put Sipgate back on an old VoIP adapter (HT-496)and there it works flawless. I had hoped to combine it on the the OBI and save one adapter and one phone standing round but cannot get it to work. It's all behind an E3000 running tomato.
I give up for now.