Text only | Text with Images

OBiTALK Community

General Support => Day-to-Day Use => Topic started by: Judgeless on January 14, 2012, 04:41:47 PM

Title: Busy signal when I call a # on one OBI device but not the other.
Post by: Judgeless on January 14, 2012, 04:41:47 PM
I have an odd issue.  I have two OBI110's.  Both with seperate Google Voice accounts.  When I try to call my land line from OBI110(2) I get a busy signal.  When I try calling the same number with OBI110(1) it works everytime.  With OBI110(2) I can call other numbers and they work.  Any idea what is going on?

I have done factory resets on OBI110(2) many times and this issue will not go away.  When I first created the OBITalk login for OBI110(2) I used the number I am trying to call as the profile name.  Could that have anything to do with it?
Title: Re: Busy signal when I call a # on one OBI device but not the other.
Post by: Judgeless on January 14, 2012, 05:09:29 PM
I did a syslog on OBI(2) when I try to make the call.  This is it.  This is the unit that fails.

2012-01-14 20:06:42   Kernel.Debug   10.0.0.30    [SLIC]:Slic#0 OFF HOOK
2012-01-14 20:06:42   Kernel.Debug   10.0.0.30    [CPT] --- FXS h/w tone generator (dial)---
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 3 @ 215400 ms----
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 215460 ms ----
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 215680 ms----
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 215750 ms ----
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 215890 ms----
2012-01-14 20:06:45   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 215960 ms ----
2012-01-14 20:06:46   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 6 @ 216300 ms----
2012-01-14 20:06:46   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 216350 ms ----
2012-01-14 20:06:46   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 0 @ 216750 ms----
2012-01-14 20:06:46   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 216820 ms ----
2012-01-14 20:06:47   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 217110 ms----
2012-01-14 20:06:47   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 217170 ms ----
2012-01-14 20:06:47   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF ON (level:1) : 9 @ 217460 ms----
2012-01-14 20:06:47   Kernel.Debug   10.0.0.30    [DSP]: ---- H/W DTMF OFF @ 217530 ms ----
2012-01-14 20:06:49   Kernel.Debug   10.0.0.30    GTT:call state changed from 0 to 2
2012-01-14 20:06:49   Kernel.Debug   10.0.0.30    GTALK:sess callsess_6 state changed from 0 to 2
2012-01-14 20:06:49   Kernel.Debug   10.0.0.30    [CPT] --- FXS h/w tone generator (reorder)---
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:Candidate 4a7d9d7e:443(5);2 2
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:Candidate 4a7d9d7e:19294(6);2 1
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:Candidate 4a7d9d7e:19295(10);2 0
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:Total peer candidates:3
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTT:call state changed from 2 to 6
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    [CPT] --- FXS h/w tone generator (ringback)---
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    RTP:Connecting->4a7d9d7e:443
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    RTP:Close tcp Channel
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    RTP:Start->4a7d9d7e:19295(80);0;0;0:0:0;1(36)
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:Call termniated : Caller disconnected [s=0]
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    GTALK:sess callsess_7 state changed from 2 to 6
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    [CPT] --- FXS h/w tone generator (reorder)---
2012-01-14 20:06:50   Kernel.Debug   10.0.0.30    RTP:Del Channel
2012-01-14 20:06:57   Kernel.Debug   10.0.0.30    [SLIC]:Slic#0 ONHOOK
Title: Re: Busy signal when I call a # on one OBI device but not the other.
Post by: Judgeless on January 14, 2012, 05:13:20 PM
This is how it looks on OBI110(1).  This one always works.

2012-01-14 20:13:08   Kernel.Debug   10.0.0.24    [SLIC]:Slic#0 OFF HOOK
2012-01-14 20:13:08   Kernel.Debug   10.0.0.24    [CPT] --- FXS h/w tone generator (dial)---
2012-01-14 20:13:11   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 3 @ 48970 ms----
2012-01-14 20:13:11   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 49040 ms ----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 49460 ms----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 49530 ms ----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 49640 ms----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 49710 ms ----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 6 @ 49990 ms----
2012-01-14 20:13:12   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 50050 ms ----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 0 @ 50420 ms----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 50480 ms ----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 50750 ms----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 50820 ms ----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF ON (level:1) : 9 @ 51070 ms----
2012-01-14 20:13:13   Kernel.Debug   10.0.0.24    [DSP]: ---- H/W DTMF OFF @ 51130 ms ----
2012-01-14 20:13:15   Kernel.Debug   10.0.0.24    GTT:call state changed from 0 to 2
2012-01-14 20:13:15   Kernel.Debug   10.0.0.24    GTALK:sess callsess_3 state changed from 0 to 2
2012-01-14 20:13:15   Kernel.Debug   10.0.0.24    [CPT] --- FXS h/w tone generator (reorder)---
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    GTALK:Candidate 4a7d9d7e:443(5);2 2
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    GTALK:Candidate 4a7d9d7e:19294(6);2 1
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    GTALK:Candidate 4a7d9d7e:19295(10);2 0
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    GTALK:Total peer candidates:3
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    GTT:call state changed from 2 to 6
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    [CPT] --- FXS h/w tone generator (ringback)---
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    RTP:Connecting->4a7d9d7e:443
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    TCP:Connect OK(rtpssl)31
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    RTP:Close tcp Channel
2012-01-14 20:13:16   Kernel.Debug   10.0.0.24    RTP:Start->4a7d9d7e:19295(80);0;0;0:0:0;1(30)
2012-01-14 20:13:20   Kernel.Debug   10.0.0.24    [DAA]: FXO ring on
2012-01-14 20:13:26   Kernel.Debug   10.0.0.24    [SLIC]:Slic#0 ONHOOK
2012-01-14 20:13:26   Kernel.Debug   10.0.0.24    GTALK:sess callsess_4 state changed from 2 to 6
2012-01-14 20:13:26   Kernel.Debug   10.0.0.24    RTP:Del Channel
2012-01-14 20:13:31   Kernel.Debug   10.0.0.24    [DAA]: FXO ring off
Title: Re: Busy signal when I call a # on one OBI device but not the other.
Post by: RonR on January 14, 2012, 07:03:00 PM
Does the same thing happen when you place those calls from the respective Google Voice web pages?  If so, it's an issue with Google Voice and not the OBi.
Title: Re: Busy signal when I call a # on one OBI device but not the other.
Post by: Judgeless on January 15, 2012, 07:53:04 AM
I did and I had the same issue.

I created a new gmail account, new google voice account and a new OBiTalk account.  It works fine now.
Text only | Text with Images