I tried very hard to get obi100 to work with voipraider, but always got the following message:
Register Failed: Server Not Reachable
Here is the Software configuration General for voipraider
SIP port : 5060
Registrar : sip.Voipraider.com
Proxy server : sip.Voipraider.com
Outbound proxy server : leave empty
Account name : Voipraider username
Password : Voipraider password
Display name/number : Voipraider username or voipnumber
Stunserver (option) : stun.Voipraider.com
What I did is:
Service Providers -> ITSB profile B -> ProxyServer : sip.Voipraider.com
Voice Services -> SP2 service -> X_ServProvProfile : B
Voice Services -> SP2 service -> AuthUserName : Voipraider username
Voice Services -> SP2 service -> AuthPassword : Voipraider password
Can any guru help me out? Thanks!
How 'bout this one?:
Service Providers -> ITSP Profile B -> SignalingProtocol : SIP
From your PC, can you ping sip.Voipraider.com?
Any item I didn't mention in my previous post takes default value. So
Service Providers -> ITSP Profile B -> SignalingProtocol : SIP
The ping results:
C:>ping sip.voipraider.com
Pinging sip.voipraider.com [77.72.169.134] with 32 bytes of data:
Reply from 77.72.169.134: bytes=32 time=176ms TTL=241
Reply from 77.72.169.134: bytes=32 time=214ms TTL=241
Reply from 77.72.169.134: bytes=32 time=222ms TTL=241
Reply from 77.72.169.134: bytes=32 time=197ms TTL=241
Ping statistics for 77.72.169.134:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 222ms, Average = 202ms
It appears you're setting things up correctly.
You might trying setting the ProxyServer to 77.72.169.129 as a shot in the dark (that's what I get for an IP address for sip.voipraider.com).
Without doing anything, amazingly, the status becomes Registered. I made a test call and it passed too. Is it possible the Obi100 default DNS had some problem? Or it takes some time to find the correct IP for sip.coipraider.com?
If the OBi is set for DHCP, the OBi DNS server is probably set to your router. Maybe the cache was bad somehow. If it happens again, try using the IP address for the Proxy Server rather than its hostname.