Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem parsing Android 4 client data #34

Open
GoogleCodeExporter opened this issue Jul 4, 2015 · 2 comments
Open

Problem parsing Android 4 client data #34

GoogleCodeExporter opened this issue Jul 4, 2015 · 2 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1.Trying to use asterisk from Gtalk to internal SIP

What version of the product are you using? On what operating system?
I'm on debian sqeeze, with libiksemel3 (1.2-4) package, but also with compiled 
version from lastest sources can  reproduce the problem.
The Android version is Android IceCream Sandiwch 4.0 with Google Talk 
4.0.3-239410 (330)


Essentially iksemel can't parse the android client data, the error from 
asterisk is "chan_gtalk.c:2005 gtalk_parser: No attribute "type" found.  
Ignoring message."

the problem is that "iks_find_attrib(pak->query, "type")" returns null

I attach the full log with some Android client data.

I'm pretty sure that it is an iksemel issue (or/combined with Android client 
issue) because with emphaty from desktop with the same google account there are 
no problems.

(sorry for my bad english)

Original issue reported on code.google.com by racing.i...@gmail.com on 1 Feb 2012 at 12:02

Attachments:
@GoogleCodeExporter
Copy link
Author 

Can be closed, it's not a iksemel bug, but an Android/Asterisk one.

Android close </jingle> tag before open <session>, so Asterisk have to check if 
there is an <session> tag after <jingle> one, and it did this only with 
<ses:session> and <jin:jingle>.

Original comment by racing.i...@gmail.com on 2 Feb 2012 at 11:55

@GoogleCodeExporter
Copy link
Author 

I have the same error. Is it reported as a Asterisk bug? Is there a workaround?

Original comment by t...@mima.x.se on 9 Feb 2012 at 9:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter