Incoming Obi calls to use VOIP provider's voicemail (call forking to voip.ms)
infin8loop:
Quote from: RonR on December 07, 2011, 12:02:27 pm
Can you bypass your router momentarily?
Not anytime soon. I have to wait until The Others leave the house.
I just thought I had no life and then I bought an OBi and now I know it.
RonR:
BTW,
You misspelled novice:
Run for your lives before this nevice sucks your brain out.
infin8loop:
Quote from: RonR on December 07, 2011, 12:28:26 pm
BTW,
You misspelled novice:
Run for your lives before this nevice sucks your brain out.
It's "device" or .... maybe I should be offended. LOL
RonR:
Quote from: infin8loop on December 07, 2011, 02:12:46 pm
It's "device"
After zooming the screen I now see what looked like an 'n' is a 'd'.
infin8loop:
Quote from: RonR on December 07, 2011, 12:02:27 pm
Can you bypass your router momentarily?
I was able to remove the router and connect the OBi110 directly to the cable modem. The SP2(883510000000091@sip.inum.net) speed dial works (with sound) when the router is out of the equation. Using the router, I've tried port forwarding 5060-5061 and 16600-16998 to the OBi and calls connect but no sound. Neither putting the OBi in the router DMZ nor using a STUN server on the OBi fixes the issue. When forwarded or in the DMZ the ports are exposed to the outside world per ShieldsUp! port probe at www.grc.com. The router is a first generation wired Netgear RP614 with the most current firmware available dated Dec 2003 (pause to let the laughter stop). Oddly (or maybe not) with the router in place, speed dial SP2(18004444444@sip.tollfreegateway.com) works!
Observing the OBi Call Status on calls to each of these speed dials I noticed that the RTP stream for calls to sip.inum.net are established on Peer RTP Address 81.201.82.41 while the IP address of sip.inum.net is 81.201.82.25 (different) and they get the no sound issue. On calls to sip.tollfreegateway.com the RTP stream is established on Peer RTP Address 76.10.223.207 and the IP address for sip.tollfreegateway.com is the same, 76.10.223.207 and the calls work with sound. Not sure if this is a coincidence or not.
I swapped a wireless Trendnet TEW-432BRP router in to be the only router (normally it just hangs off the Netgear with DHCP disabled as a wireless AP). The Trendnet's most currently available firmware is dated Dec 2007 (I know --- more laughter ensues). Going through the same rigmorole on the Trendnet of port forwarding, or DMZ, or STUN server, and it behaves the same way.. no sound on the sip.inum.net calls.
SP2 is still configured for voip.ms and works with "normally" dialed calls (not sip uri). Are these routers functioning like a roach motel with RTP packets checking in and not checking out? With the Netgear router in place I can call the Houston iNum PSTN access number using my cellphone and enter my voip.ms issued iNum and the call comes through on the OBi with sound on both ends. My daughter had her friend in the Netherlands call the Amsterdam iNum PSTN access number and enter the same iNum number and that call rang thorough on the OBi, but when answered, no sound on either end. I didn't catch the Call Status on that call. They were also on a Skype video chat at the time so we could tell what was happening. They were impressed but would have been even MORE impressed had they been actually able to talk to each other on the phone!
Sinterklass did not bring me a new router nor did I get my initial in dreamy chocolate. I'm considering the Linksys WRT54GL. At this point I really don't need gigabit. Of course the minute I say that, I'll probably need it. Would this router most likely solve my issues? I say "most likely" because I haven't fully ruled out the possibility I have no clue what I'm doing. Yes, perhaps I'm still a "novice" and it's not just the "device" ;-) I'm open to other voip friendly router suggestions.
Navigation
[0] Message Index
[#] Next page
[*] Previous page