| |
[Asterisk] GV call in asterisk does not work againGV call in asterisk does not work again. They are playing the same game as last time. Now it needs to apply the patch we used last time. |
|
| |
MichiganTel
Anon
2011-Oct-13 8:53 am
Thanks for the heads-up. Guess it's time to apply the patch again. Note that the revised patch as described in this blog post will allow outgoing calls to work whichever of the two methods Google Voice happens to be using on any particular day. So after you apply that fix, if they flip-flop again you won't have to do anything to make the calls work. |
|
1 edit |
said by MichiganTel :Thanks for the heads-up. Guess it's time to apply the patch again.
Note that the revised patch as described in this blog post will allow outgoing calls to work whichever of the two methods Google Voice happens to be using on any particular day. So after you apply that fix, if they flip-flop again you won't have to do anything to make the calls work. Thanks for the information. That will be very helpful. Your link does not work. Could you provide a valid link? Thanks. Update: I found the linked blog. It's really useful. Thanks. |
|
maziloFrom Mazilo Premium Member join:2002-05-30 Lilburn, GA |
mazilo
Premium Member
2011-Oct-13 9:27 am
I just successfully called my GV number and it worked without a problem. Of course, my GV is configured through my FreeSWITCH PBX System using mod_dingaling.  said by davidnewt:Your link does not work. Could you provide a valid link? The link is about an old article dated on 08/19/2011. |
|
| |
MichiganTel
Anon
2011-Oct-13 9:40 am
Sorry about the bad link - thank you mazilo for correcting it, though I'm not sure why you'd refer to a page created less than two months ago as "old". The information is still as valid as it was then, except that Asterisk has been upgraded a couple of times since then, so some users may need to change the version references to whatever version of Asterisk they are now running. |
|
| |
Thanks for both of you. The link is really helpful since it will avoid the same problem GV's game caused. I am compiling this patch right now and hopefully next time GV plays the same game, I don't need to worry about if my calls can reach their destination. |
|
|
maziloFrom Mazilo Premium Member join:2002-05-30 Lilburn, GA |
to MichiganTel
said by MichiganTel :..., though I'm not sure why you'd refer to a page created less than two months ago as "old". IC your point. I thought GV made another changes again. |
|
| |
to davidnewt
This is getting to be annoying. Last time they changed something and then went back. I upgraded asterisk to 1.8.6.0 which is the latest available on optware. I'm running asterisk on tomatousb. Does anyone have a patched pkg available for optware? Thanks. |
|
| |
said by bhairya:This is getting to be annoying. Last time they changed something and then went back. I upgraded asterisk to 1.8.6.0 which is the latest available on optware. I'm running asterisk on tomatousb. Does anyone have a patched pkg available for optware? Thanks. It will be not easy for optware since the compilation depends on other people who is in charge of optware. Hopefully someone can figure out how to compile optware packages to make the patch work. I don't know why GV keeps playing this kind of game. Too bad. |
|
maziloFrom Mazilo Premium Member join:2002-05-30 Lilburn, GA |
to bhairya
said by bhairya:This is getting to be annoying. Indeed. Apparently, this had happened a few times in the past to (ONLY) Asterisk users when every time Google Voice made some changes, IIRC. Last time they changed something and then went back. I upgraded asterisk to 1.8.6.0 which is the latest available on optware. I'm running asterisk on tomatousb. Does anyone have a patched pkg available for optware? If you wannabe on top to solve issue like this, your best chance is to switch to OpenWRT and build your own firmware from source. This will include building the GCC cross compiler and use it to compile the firmware. When you do this, you can include Asterisk packages with its dependent library packages into the firmware (eliminating guessing works as to which libraries are needed to install to make Asterisk work properly). Unless your device can boot off of an external USB partition and/or LAN, then this means your device needs to have enough storage to receive a bigger firmware. I build my own OpenWRT firmware for my Seagate DockStar to include FreeSWITCH, a USB printer server, Samba, and among other software packages for it to serve my needs. |
|
| |
to MichiganTel
said by MichiganTel :Thanks for the heads-up. Guess it's time to apply the patch again.
Note that the revised patch as described in this blog post will allow outgoing calls to work whichever of the two methods Google Voice happens to be using on any particular day. So after you apply that fix, if they flip-flop again you won't have to do anything to make the calls work. MichiganTel: I have compiled the new 1.8.7.0 version with the patch from your blog. It works very well right now. Let's see how it goes when GV flip back next time. Hopefully next time when GV flip-flop again, the problem will be handled automatically. Thanks a lot for the information. |
|
| |
to mazilo
mazilo, I'm using my dockstar as mainly a file server with a few USB drives attached to it. I've got plugbox linux on it at the moment. I've seen your posts about freeswitch but I had already gone the plugbox way. I installed asterisk on my tomatousb Asus RT-N16 via optware on a USB drive. I've been running this for quite a while now and, except for these annoying issues Google keeps creating, it's been good for the most part. The thought of reading all this stuff again and the new howtos for freeswitch and openwrt seem like so much work right now. I could look into building a dev environment for the ipkg system optware uses, but even that seems like a lot of work. I might just wait for google to either go back or for the optware pkg to get updated. It's quite annoying just the same.  |
|
| |
said by bhairya:mazilo, I'm using my dockstar as mainly a file server with a few USB drives attached to it. I've got plugbox linux on it at the moment. I've seen your posts about freeswitch but I had already gone the plugbox way. I installed asterisk on my tomatousb Asus RT-N16 via optware on a USB drive. I've been running this for quite a while now and, except for these annoying issues Google keeps creating, it's been good for the most part. The thought of reading all this stuff again and the new howtos for freeswitch and openwrt seem like so much work right now. I could look into building a dev environment for the ipkg system optware uses, but even that seems like a lot of work. I might just wait for google to either go back or for the optware pkg to get updated. It's quite annoying just the same.  If you already have plugbox linux running on the dockstar, then it is very easy to install asterisk on it. Probably takes about 30 minutes for compiling. Then you have control by yourself if there is a problem. Here is an good instruction from twinclouds. It works on both debian and plugbox linux and you don't need to wait for optware maintainers to update. Good luck. » forums.plugpbx.org/index ··· 6.0.htmland » forums.plugpbx.org/index ··· 7.0.html |
|
| |
Cool thanks, I'll check it out. |
|
| |
Here is a asterisk1.8.7.0 deb file working for debian squeeze on dockstar. This package includes the patch to handle both cases from GV. Hope this helps for people who have problem to compile the patch. |
|
| |
to davidnewt
I'm running it from optware as well, shame its not fixed yet. I do hope they incorporate the patch next release so things do not flip flop so much (: I'm relieved that the problem is not on my end, and that there is a fix in the works. Happy calling everyone |
|
nunyaLXI 483 MVM join:2000-12-23 O Fallon, MO |
to davidnewt
|
|
| |
to davidnewt
Is there a way to find out when a new version of asterisk is released for optware? |
|
| |
optware asterisk usually does not issue new version until asterisk itself has new release. Since this patch is not official from asterisk, the optware might not be updated at this moment. |
|
EyesOnly join:2011-10-13 Saint-Constant, QC 1 edit |
to bhairya
bhairya, mrdally204, screenname, For those running asterisk on optware, you might want to try this file. Uncompress and place chan_gtalk.so in /opt/lib/asterisk/modules I have tested it on a RT-N16 and now GV calls are back to normal. Hope it works for you guys! EyesOnly |
|
3 edits |
Didn't work for me.
EDIT: I found out I am able to make toll free (877,888) calls. Just not the "regular" calls. |
|
EyesOnly join:2011-10-13 Saint-Constant, QC |
arrg same for me... I was too quick into thinking it worked, it feelback to the next trunk  We have to wait for the next release I guess  EyesOnly |
|
| |
to davidnewt
Nice try, thanks for the effort! |
|
XCOMdigitalnUll Premium Member join:2002-06-10 Spring, TX (Software) pfSense MikroTik CRS125-24G-1S-RM
|
XCOM
Premium Member
2011-Oct-19 11:04 am
|
|
| |
Thanks XCOM, not really sure what to do with it though. Never compiled and wouldn't know where to even start for optware. |
|
EyesOnly join:2011-10-13 Saint-Constant, QC 1 edit |
Hi guys, I managed to compile asterisk-1.8.7.0 on optware, with the GV patch and with SRTP. Backup your files, especially /opt/etc/asterisk stop asterisk process ipkg remove asterisk18 (carefull it removes all config files) and install the files from the archive to /opt copy your backup /opt/etc/asterisk config files back to /opt/etc/asterisk restart asterisk Tested all morning on my router. If it does not work then you can remove files in /opt/lib/asterisk/modules and /opt/include/asterisk and ipkg install asterisk18 with your config files Edit: updated archive to include xmldocs EyesOnly |
|
1 edit |
Thanks. Able to make one complete call on the first try. When it starts up, I got whole bunch of erros from xmldoc.c
WARNING[6613]: xmldoc.c:1789 xmldoc_build_field: Couldn't find function IFTIME in XML documentation |
|
EyesOnly join:2011-10-13 Saint-Constant, QC 1 edit |
Screenname,
Try adding the contents of this archive to /opt and let me know if this fixes the xmldoc errors...
edit: removed file no longer needed, included in asterisk-1.8.7.0-1.tar.gz
EyesOnly |
|
| |
EyesOnly, Thanks. That fixed it. |
|
| |
to davidnewt
I have yet to try it but thanks a bunch! Might want to talk to the optware people and let them offer your compile  Might help a few others as well! |
|