Summary: | ASTERISK-18845: chan_gtalk only receives calls from Gtalk Android but not viceversa | ||
Reporter: | Augusto Henrique Petzinger (apetzinger) | Labels: | |
Date Opened: | 2011-11-09 16:51:16.000-0600 | Date Closed: | 2015-02-26 09:26:29.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_gtalk Resources/res_jabber |
Versions: | 1.8.7.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Centos 5.7 2.6.18-274.7.1.el5 | Attachments: | ( 0) Android-Gtalk.jpg ( 1) android-gtalk.patch ( 2) debug.asterisk.log ( 3) gtalk.conf ( 4) jabber_show_buddies.log ( 5) jabber.conf |
Description: | The client android (gtalk) support voice and video, is ginglerbread 2.3.7, and version is 1.3. Asterisk normally receive voice calls, but not viceversa. Asterisk can't make voice call to android gtalk client!! I think it has to do with Jingle capable: no, because the client's Web gtlak is yes, but the Android client is "NO" | ||
Comments: | By: Augusto Henrique Petzinger (apetzinger) 2011-11-09 17:03:39.816-0600 Please note... Android Jingle capable = NO Web Jingle capable = YES Buddy: augusto@status.com.br Resource: android4f0e45dbb3ea node: http://www.android.com/gtalk/client/caps version: 1.1 Jingle capable: no Status: 3 Priority: 24 Resource: gmail.713CEFFB node: http://mail.google.com/xmpp/client/caps version: 1.1 Jingle capable: no By: Augusto Henrique Petzinger (apetzinger) 2011-11-09 17:05:36.477-0600 Please see ASTERISK-18084 By: Dave Bowerman (dbowerman) 2012-02-29 20:52:07.747-0600 Please try the attached patch. Ive tested this with an android device that has a front facing camera, so voice and video. Non-video devices may need and extra patch. By: Malcolm Davenport (mdavenport) 2015-02-26 09:26:29.527-0600 Unfortunately, no response was received from the reporter during the bug-fix period for 1.8. As support for XMPP and Google was rewritten completely in Asterisk 11 with chan_motif and res_xmpp, the results there may be completely different. Thus, I'm closing out this issue. |