Asterisk 1.8+Google Voice fixed

| No Comments | No TrackBacks
The Asterisk team released a small patch that fixes the protocol issue that was keeping Asterisk 1.8 users from dialing out through Google Voice.

You can apply the patch against version 1.8.0 or 1.8.1. And if you've never used the patch command before, it's easy:

  • Go to the Asterisk bug tracker and get the attached file named fix

  • Put it in your Asterisk source directory (the root, where the configure script, Makefile, and other such files exist). Call it gtalkfix.patch, to be a little less ambiguous.

  • From that same directory, run the command patch < gtalkfix.patch . If it says it can't find the file to patch, specify channels/chan_gtalk.c. Oh, and if you don't have the patch command, just yum install patch first.

  • You should see something like this:
    patching file channels/chan_gtalk.c
    Hunk #1 succeeded at 193 with fuzz 2 (offset -3 lines).
    Hunk #2 succeeded at 463 (offset -5 lines).
    Hunk #3 succeeded at 1006 (offset -3 lines).
    Hunk #4 succeeded at 1814 (offset -5 lines).


  • Now run make and you will see it compile chan_gtalk again. Of course, if you are applying it against the raw distribution, you'll go through the entire build process.

  • make install and start Asterisk and you'll be able to call through Google Voice again.

No TrackBacks

TrackBack URL: https://blogs.psu.edu/mt4/mt-tb.cgi/214555

Leave a comment

Subscribe to receive notifications of follow up comments via email.
We are processing your request. If you don't see any confirmation within 30 seconds, please reload your page.

February 2012

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29      

Contact Me


AIM: TNS BillS

View William Simon's profile on LinkedIn

Donate

Make a gift
Like this blog? Support education and research at Penn State by donating any amount to an area of your choice.

Subscribe

Blogroll

Disclaimer

We are Penn State, but I am not. Opinions expressed on this blog are those of the author and do not represent the opinions of The Pennsylvania State University or any division therein, including but not limited to the author's workgroup, department, administrative unit, or campus. Technologies and ideas discussed on this blog do not describe a production service unless noted.