December 11, 2018, 02:57:18 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Frequent call drops using Obi100+google voice  (Read 9914 times)
belledion
Newbie
*
Posts: 2


« on: July 12, 2011, 11:25:06 am »

Hi all,

I just installed Obi100 to use google voice, but found out the call drops are way to0 frequent! It seems the call would get dropped every 4 or 5 minutes. I tried both a local number and a 800 number and the "5 minute drop rule" applies to both scenarios, giving me 6 drops in total! Does anyone have any idea why this happens? I can barely use obitalk+GV if it keeps dropping calls like this  Sad

Thanks!
Logged
RonR
Hero Member
*****
Posts: 4527


« Reply #1 on: July 12, 2011, 12:04:22 pm »

Routers are always suspects in these cases.  If possible, temporarily connect the OBi directly to your broadband modem and see if the problem goes away.

Sometimes forwarding SIP (5060 - 5061) and RTP (16600 - 16998) ports in the router to the OBi will help if the router is the source of the problem.
Logged
belledion
Newbie
*
Posts: 2


« Reply #2 on: July 14, 2011, 01:26:14 pm »

thanks for the suggestion!

could you tell me how to do the port forwarding?
« Last Edit: July 14, 2011, 01:37:38 pm by belledion » Logged
jimates
OBi110 Beta Testers
***
Posts: 1610


« Reply #3 on: July 14, 2011, 09:14:04 pm »

thanks for the suggestion!

could you tell me how to do the port forwarding?


You need to make sure the router is the problem. To verify this connect the Obi directly to the modem without the router. Power cycle the modem after connecting the Obi to it.
Logged
RonR
Hero Member
*****
Posts: 4527


« Reply #4 on: July 14, 2011, 09:43:25 pm »

could you tell me how to do the port forwarding?

Port forwarding is done through the user interface of your router.  Specific details would have to come from your router's User Guide or Help files.

In general, you forward a port or range of ports to a specific IP address.  For this reason, the OBi would need to have a consistent IP address.  Some routers consistently assign the same IP address via DHCP to a particular device, others do not.  If your OBi doesn't get a consistent IP address via DHCP, you may be able to configure your router to assign one via Static DHCP.  Otherwise, you would have to configure your OBi for a Static IP address.

The Port Forwarding entries in your router would look something like:

Name    Port Range       Destination     Protocol

SIP        5060-5061      192.168.1.x    Both
RTP      16600-16998    192.168.1.x    Both

where 192.168.1.x is the actual IP address assigned to your OBi.
Logged
bruss
Jr. Member
**
Posts: 41



« Reply #5 on: July 18, 2011, 12:12:35 pm »

what if you have multiple obis?
Logged
RonR
Hero Member
*****
Posts: 4527


« Reply #6 on: July 18, 2011, 12:53:06 pm »

what if you have multiple obis?

I set the second OBi as follows:

Voice Services -> SP1 Service -> X_UserAgentPort : 5062

Voice Services -> SP2 Service -> X_UserAgentPort : 5063

Service Providers -> ITSP Profile A -> RTP -> LocalPortMin : 17600
Service Providers -> ITSP Profile A -> RTP -> LocalPortMax : 17798

Service Providers -> ITSP Profile B -> RTP -> LocalPortMin : 17800
Service Providers -> ITSP Profile B -> RTP -> LocalPortMax : 17998
Logged
GnatGoSplat
Jr. Member
**
Posts: 23


« Reply #7 on: July 23, 2011, 06:54:30 pm »

I'm suddenly having this same problem after updating to the latest firmware.  I have no idea what version of firmware I was on before.  It drops the call and goes to a dialtone.  All subsequent attempts to call out results in a service is not available message until I unplug and replug the Obi.  OP, did you find a solution?

I am going to see if I can downgrade the firmware.  Unfortunately, I don't know what version I was on before that had been working perfectly up until today.
Logged
OBiSupport
Administrator
****
Posts: 259


« Reply #8 on: July 25, 2011, 09:12:27 am »

Please contact Obihai support at: supprt@obihai.com, and state your 9-digit number along with the problem description, we will help you solve this problem. Thank you,
Logged
GnatGoSplat
Jr. Member
**
Posts: 23


« Reply #9 on: July 25, 2011, 09:18:14 am »

I'm not positive, but I may have fixed this problem by upgrading to newest firmware and then setting to factory defaults and setting back up by hand.
One problem I had before resetting to factory defaults is I was getting a stylesheet error in the main frame when browsing to the Obi's web admin page, but after factory defaults, it loads correctly now.
I will need to give it a few more days before I know for sure it is fixed.
Logged
OBiSupport
Administrator
****
Posts: 259


« Reply #10 on: July 25, 2011, 09:43:49 am »

The latest firmware have much improved GV call reliability, please inform us if you experience any problem.
Logged
sandy6wan9obi
Newbie
*
Posts: 1


« Reply #11 on: August 05, 2011, 04:36:34 pm »

had the same issue, but it is resolved by opening port 5060.

but not sure it's a good idea to open 398 port for rtp tho. 

Name    Port Range       Destination     Protocol

SIP        5060-5061      192.168.1.x    Both
RTP      16600-16998    192.168.1.x    Both
Logged
GnatGoSplat
Jr. Member
**
Posts: 23


« Reply #12 on: August 06, 2011, 08:27:55 am »

Unfortunately, my problem didn't go away even with a reset to factory defaults and setting everything back up by scratch.

Thanks sandy, I've set up port range forwarding on my router as you've specified and I hope that will fix it.

I just don't understand why the original shipped firmware on my Obi100 worked perfectly and flawlessly for months, then as soon as I updated the firmware, everything goes to crap.  That goes for the last two versions.  I hadn't made any changes to my router settings before now.
Logged
ChrisThompson
Jr. Member
**
Posts: 21


« Reply #13 on: August 08, 2011, 02:33:22 pm »

I've been having this problem as well.  I setup the suggestion ports to forward directly to the Obi110, but I'm still getting dropped calls.

Here's a log from an incident that just happened.  It was an incoming call that dropped after about 20 minutes.  (the log starts with the call dropping), then they called back, I answered but couldn't hear them. They called back a third time, and the call dropped within about 2 minutes.  I ended up just picking up my cell phone the next time using the T-Mobile USA Wi-Fi Calling app and didn't have any issues.

Code:
Aug  8 15:09:03  XMPP: Updating peer:jleonard.dtiglobal@gmail.com[TalkGadget2CC2B113] to online
Aug  8 15:10:04  XMPP: Updating peer:dtiglobal@thompson-web.org[android3d56f45f05c3] to online
Aug  8 15:12:02  XMPP: Updating peer:dtiglobal@thompson-web.org[android3d56f45f05c3] to online
Aug  8 15:13:38  GTALK: sess SIP1644278913@10.229.66.68 state changed from 5 to 6
Aug  8 15:13:38  RTP: Del Channel
Aug  8 15:13:38  [JB] call overall status --      #012peer:             74.125.127.126:19295(relay),#012local:            192.168.1.144:63826,#012pkt_tx:           106535,#012pkt_rx:           103576,#012bytes_tx:         18323552,#012bytes_rx:         17815072,#012clk_diff:         30 PPM,#012pkt_in_jb:        0,#012pkt_ooo:          17,#012pkt_lost:         51,#012pkt_late:         12,#012pkt_loss_rate:    0 %,#012pkt_drop_rate:    0 %,#012jb_len:           190 ms,#012curr_rcvd_jitter: 10 ms,#012rcvd_digits:      0,#012underruns:        12,#012overruns:         0,#012seq_num_broken:   57,#012pkt_interp:       5956,#012skew_comp:        -40 ms,#012frm_in_pkt:       2
Aug  8 15:13:42  [SLIC]: Slic#0 HOOK FLASH
Aug  8 15:13:42  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:13:42  [CPT] --- FXS h/w tone generator (dial)---
Aug  8 15:13:45  [SLIC]: Slic#0 ONHOOK
Aug  8 15:13:45  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:13:49  [SLIC]: Slic#0 OFF HOOK
Aug  8 15:13:49  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:13:49  [CPT] --- FXS h/w tone generator (dial)---
Aug  8 15:13:52  [SLIC]: Slic#0 ONHOOK
Aug  8 15:13:52  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:14:26  TCP: Connect OK(HTTP GET)42
Aug  8 15:14:26  Update Config Now ...
Aug  8 15:14:26  XML_parse_prov 0
Aug  8 15:14:26  PARAM: Notification sent: 0
Aug  8 15:14:26  Same version:  Skipped (2)
Aug  8 15:14:26  TCP: Connect OK(HTTP GET)44
Aug  8 15:14:26  Update Config Now ...
Aug  8 15:14:26  XML_parse_prov 0
Aug  8 15:14:26  PARAM: Notification sent: 0
Aug  8 15:14:26  Same version:  Skipped (2)
Aug  8 15:14:26  We will check new config in 3600 s
Aug  8 15:14:44  GTALK: sess SIP1559229106@10.13.171.13 state changed from 0 to 3
Aug  8 15:14:44  [SLIC] CID to deliver: ''
Aug  8 15:14:44  GTT: call state changed from 0 to 5
Aug  8 15:14:44  GTALK: sess SIP1559229106@10.13.171.13 state changed from 3 to 4
Aug  8 15:14:45  GTALK: Candidate 4a7d7f7e:443(5);2 2
Aug  8 15:14:45  GTALK: Candidate 4a7d7f7e:19294(6);2 1
Aug  8 15:14:45  GTALK: Candidate 4a7d7f7e:19295(10);2 0
Aug  8 15:14:45  GTALK: Total peer candidates:3
Aug  8 15:14:49  [SLIC]: Slic#0 OFF HOOK
Aug  8 15:14:49  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:14:49  GTALK: sess SIP1559229106@10.13.171.13 state changed from 4 to 5
Aug  8 15:14:49  RTP: Connecting->4a7d7f7e:443
Aug  8 15:14:49  GTT: call state changed from 5 to 3
Aug  8 15:14:49  TCP: Connect OK(rtpssl)48
Aug  8 15:14:49  RTP: Start->4a7d7f7e:19295(80);0;0;0:0:0;1(47)
Aug  8 15:14:49  RTP: Skt Connected
Aug  8 15:14:50  RTP: PeerRflxAddr=4a7d7f7e:19295
Aug  8 15:15:04  [SLIC]: Slic#0 ONHOOK
Aug  8 15:15:04  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:15:04  GTALK: sess SIP1559229106@10.13.171.13 state changed from 5 to 6
Aug  8 15:15:04  RTP: Del Channel
Aug  8 15:15:04  [JB] call overall status --      #012peer:             74.125.127.126:19295(relay),#012local:            192.168.1.144:56372,#012pkt_tx:           758,#012pkt_rx:           72,#012bytes_tx:         129908,#012bytes_rx:         12224,#012clk_diff:         0 PPM,#012pkt_in_jb:        0,#012pkt_ooo:          0,#012pkt_lost:         0,#012pkt_late:         0,#012pkt_loss_rate:    0 %,#012pkt_drop_rate:    0 %,#012jb_len:           190 ms,#012curr_rcvd_jitter: 0 ms,#012rcvd_digits:      0,#012underruns:        0,#012overruns:         0,#012seq_num_broken:   0,#012pkt_interp:       1356,#012skew_comp:        0 ms,#012frm_in_pkt:       2
Aug  8 15:15:08  [SLIC]: Slic#0 OFF HOOK
Aug  8 15:15:08  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:15:08  [CPT] --- FXS h/w tone generator (dial)---
Aug  8 15:15:11  [SLIC]: Slic#0 ONHOOK
Aug  8 15:15:11  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:15:50  GTALK: sess SIP510907621@10.229.66.68 state changed from 0 to 3
Aug  8 15:15:50  [SLIC] CID to deliver: ''
Aug  8 15:15:50  GTT: call state changed from 0 to 5
Aug  8 15:15:50  GTALK: sess SIP510907621@10.229.66.68 state changed from 3 to 4
Aug  8 15:15:51  GTALK: Candidate 4a7d7f7e:443(5);2 2
Aug  8 15:15:51  GTALK: Candidate 4a7d7f7e:19294(6);2 1
Aug  8 15:15:51  GTALK: Candidate 4a7d7f7e:19295(10);2 0
Aug  8 15:15:51  GTALK: Total peer candidates:3
Aug  8 15:15:57  [SLIC]: Slic#0 ONHOOK
Aug  8 15:15:57  [SLIC]: Slic#0 OFF HOOK
Aug  8 15:15:57  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:15:57  GTALK: sess SIP510907621@10.229.66.68 state changed from 4 to 5
Aug  8 15:15:57  RTP: Connecting->4a7d7f7e:443
Aug  8 15:15:57  GTT: call state changed from 5 to 3
Aug  8 15:15:57  TCP: Connect OK(rtpssl)51
Aug  8 15:15:57  RTP: Start->4a7d7f7e:19295(80);0;0;0:0:0;1(50)
Aug  8 15:15:57  RTP: Skt Connected
Aug  8 15:15:58  RTP: PeerRflxAddr=4a7d7f7e:19295
Aug  8 15:17:00  GTALK: sess SIP510907621@10.229.66.68 state changed from 5 to 6
Aug  8 15:17:00  RTP: Del Channel
Aug  8 15:17:00  [JB] call overall status --      #012peer:             74.125.127.126:19295(relay),#012local:            192.168.1.144:47838,#012pkt_tx:           3122,#012pkt_rx:           2064,#012bytes_tx:         536516,#012bytes_rx:         354848,#012clk_diff:         80 PPM,#012pkt_in_jb:        0,#012pkt_ooo:          0,#012pkt_lost:         0,#012pkt_late:         0,#012pkt_loss_rate:    0 %,#012pkt_drop_rate:    0 %,#012jb_len:           190 ms,#012curr_rcvd_jitter: 7 ms,#012rcvd_digits:      0,#012underruns:        0,#012overruns:         0,#012seq_num_broken:   0,#012pkt_interp:       2107,#012skew_comp:        0 ms,#012frm_in_pkt:       2
Aug  8 15:17:03  [SLIC]: Slic#0 HOOK FLASH
Aug  8 15:17:03  [SLIC] CID to deliver: '(null)' (null)
Aug  8 15:17:03  [CPT] --- FXS h/w tone generator (dial)---
Logged
GnatGoSplat
Jr. Member
**
Posts: 23


« Reply #14 on: August 08, 2011, 09:46:06 pm »

The port forwarding didn't help me either.
After mine crashes, I can't even get into the log.  At least, not through the native web interface (I didn't see any log options in the Obitalk portal).  I get:

Error loading stylesheet: An unknown error has occurred (804b0014)http://192.168.10.110/default.xsl

Is there any possible way to get the version of firmware that would have come on an Obi100 that shipped in May?  The original firmware is the only one that I ever had working properly.
Logged
OBiSupport
Administrator
****
Posts: 259


« Reply #15 on: August 09, 2011, 11:05:55 am »


Is there any possible way to get the version of firmware that would have come on an Obi100 that shipped in May?  The original firmware is the only one that I ever had working properly.


If this GV call drop happens often, can you try the Gmail call phone service? and see if a similar problem appear also. We like to see if it is related to your network or GV service.

Please also contact our support team at support@obihai.com, and we like to have a close look at your device, thanks,
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC