PBXIAF/Orgasmatron GV setup outcalling stops working every so often

[isaacl]

I am using the Orgasmatron V, Google Voice Edition setup.
I have the latest version of pygooglevoice installed.
For some reason, after a day or two, outcalling with GV will just stop working. I've tried reinstalling pygooglevoice a few times, and after each time I reinstall it, it seems to work, but then again a bit later it again stops working.
Any ideas why this is happening?
Thanks!

 

[wardmundy]

I think you've posted this before with different wording. If you're using Gizmo5 as the intermediate provider, try switching to IPkall or SIPgate.

 

[isaacl]

I've been using Sipgate.
Switching didn't help anything...
I'm gonna keep playing with it, or if not, I'll set up a real DID with service

 

[donnib]

I've been using Sipgate.
Switching didn't help anything...
I'm gonna keep playing with it, or if not, I'll set up a real DID with service

I have same problem. Sometimes it works sometimes it wont. I just don't reinstall but try again next day then it works. GV is unreliable for some reason.

 

[wardmundy]

There's a lot of truth in the old adage: "You get what you pay for."

 

[donnib]

There's a lot of truth in the old adage: "You get what you pay for."

true true i got used to that. I am not complaining or maybe i am but i want to achieve is to let people know that it's an unreliable service at the moment.

 

[wardmundy]

Sorry, but many of us haven't seen the problems you are reporting. There are literally thousands of people using the Orgasmatron V build to make free Google Voice calls. You are one of less than a handful reporting any problems.

 

[isaacl]

Do you think that wiping the system, and then restoring from a backup might help?
Also, if I would want to move to a regular (non GV) system, would I need to reinstall PBXIAF, or can I just change some settings on my current setup?
Thanks!

 

[isaacl]

I'm in middle of re-installing PBXIAF now.
If I had issues with GV before, and I restore a backup, will I probably have issues again?
Or was it probably something not backed up that was messed up?

 

[shane]

I am having similar issues with GV. For example I made a call about 2 hours ago with no problems and now when I try the parking lot times me out. Google voice does not show the call connecting to them and I can call in to the PIAF box from a cell phone with no problems.

While writing this message I was finally able to make an outgoing call after 30 minutes of trying.

Not sure if this will help anyone point out what may be happening but here is the debug log for a failed call:

[2010-01-20 13:02:14] VERBOSE[15610] logger.c: -- Dial Tech,String: (Console,dsp)
[2010-01-20 13:02:14] VERBOSE[15610] logger.c: -- Call Parking Called, lot: 75, timeout: 45000, context: (null)
[2010-01-20 13:02:14] WARNING[15610] channel.c: No channel type registered for 'Console'
[2010-01-20 13:02:14] NOTICE[15610] channel.c: Unable to request channel Console/dsp
[2010-01-20 13:02:14] WARNING[15610] app_parkandannounce.c: PARK: Unable to allocate announce channel.

Could someone help educate me by explaining why these warnings are being generated?

 

[wardmundy]

This is starting to sound like either a hardware issue or a particular version of Asterisk that's causing it. Could those having problems identify your specific version of Asterisk as well as your hardware platform including brand, processor, and sound card. Also let us know if this is a virtual machine and, if so, the type. Thanks.

 

[shane]

I am using the following setup:
Dell T100 with AMD Athlon 4450B and 2G memory
Proxmox 1.4.
CentOS 5.2 64bit
Asterisk 1.4.26.2
No sound card
The VM is setup with 512MB of memory.

 

[isaacl]

I tried reinstalling my whole system today, so I still have to see if that fixed it or not.
I'm using an older computer - a eMachines T1801
P3 Celeron, 800 MHz, with 256 MB RAM
Default installation of PBXIAF as of today and Orgasmatron GV
Asterisk 1.4.21.2
CentOS 5.2 32bit
No idea what sound card...

 

[isaacl]

Any ideas or updates?
Thanks.

 

[DerekR]

Not that this helps you any, but I'm having the same problem right now after a solid 8 weeks of uptime, minus the python script install a month or so back.

I don't think the particular problem has anything to do with our boxes (I'm running an AMD 64 2.3 GHZ dual core with 2 gigs of ram and still have this issue). Course, I just ran into it today around 2 p.m. EST. At 1 p.m. EST it was working fine.

I can see that my SIPGate trunks are still all registered. Logging into their perspective accounts on SIPGate also shows them to be in working order... so it leads me to believe that the only common denominator here is Google, and that's what's causing the problem. Who know's what it is, but I fully expect everything to be online and running by tomorrow morning as though nothing happened. Hopefully. All my GV accounts are working too, though, so it all could be a crap shoot. I haven't made any changes since it last worked and I haven't been hacked, so the big mystery remains.

Stinks too! I was making some really good progress, messing with multiple lines and different routes. It's the first time I've really dug into Asterisk and I'm enjoying the difficult, but mostly rewarding ride.

EDIT: LOL! And go figure... few hours of downtime and I'm back in the game and it's working -- nothing changed in the configuration of Asterisk at all.

EDIT: And back to the drawing board today. I'm having the problem again, but it seems that it doesn't matter whether my call connects or doesn't connect, I get that error you posted earlier in the logs (identical). Tried reverting to an old backup that I knew had nothing modified other than the -py script and it's still sporadically working. I don't know what else to do at this point. I'd do a reinstall, but I really, really don't think it's the hardware or the PBX version (Assuming 1.6 on 2.5.2.2, Orgasmatron V build). I'm out of ideas at the moment, so hopefully someone else can bring some light on the situation.

 

[DerekR]

Alright, sorry for the double post, but why in the heck is this using so much memory cache? Could this be a part of the problem? I even tried a reboot and the bars just keep on climbing and climbing and climbing.

From the Sys Info section:

EDIT: Did some research on this, apparently it is completely normal for Linux to eat it all up and then use the SWAP as necessary. Duh on my part.

More system info:

Canonical Hostname pbx.dyndns.org
Listening IP 192.168.0.19
Kernel Version 2.6.18-92.1.22.el5 (SMP)
Distro Name CentOS release 5.2 (Final)
Uptime 1 minutes
Current Users 0
Load Averages 1.08 0.41 0.15

Processors 2
Model AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
CPU Speed 2.31 GHz
Cache Size 512.00 KB
System Bogomips 9244.85
PCI Devices
- Audio device: nVidia Corporation MCP61 High Definition Audio
- Bridge: nVidia Corporation MCP61 Ethernet
- Co-processor: nVidia Corporation MCP61 SMU
- Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
- Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
- Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
- Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
- IDE interface: nVidia Corporation MCP61 IDE
- (2x) IDE interface: nVidia Corporation MCP61 SATA Controller
- ISA bridge: nVidia Corporation MCP61 LPC Bridge
- (3x) PCI bridge: nVidia Corporation MCP61 PCI Express bridge
- PCI bridge: nVidia Corporation MCP61 PCI bridge
- (2x) RAM memory: nVidia Corporation MCP61 Memory Controller
- SMBus: nVidia Corporation MCP61 SMBus
- (2x) USB Controller: nVidia Corporation MCP61 USB Controller
- VGA compatible controller: nVidia Corporation GeForce 6100 nForce 430
IDE Devices none
SCSI Devices
- ATA ST3250410AS (Direct-Access)
USB Devices none


EDIT: Just tried another test call, this time it connected, and rang my cell phone, and I answered, but the softphone (x-lite) picked up nothing (no audio). It was like it had dropped the call, even though it was still connected. Also took a considerable amount of time to connect the call.

EDIT #13243534: Sooo... did some more testing. Tried out GV through the main interface and it was working fine. Then I decided to take SIPGate off the trunks and throw the credentials into X-Lite. Could not receive a call! Logged into my SIPGate account and set up a forwarder to another phone number -- and it would connect!

Doesn't make a shred of sense, but it also means it has nothing to do with Orgasmatron and everything to do with SIPGate. I've sent a customer support e-mail in, so we'll see how that goes. Did you try putting your SIPGate credentials into just a softphone to see if it connected?

 

[pbx954]

I had a similar problem a few weeks ago and its was due to the caller id module in PIAF . Try disabling it, check your file permissions, reboot and test

Cecil