[asterisk-bugs] [Asterisk 0012432]: Gtalk channel allocation fails after large number of buddy

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12432 
====================================================================== 
Reported By:                visu
Assigned To:                phsultan
====================================================================== 
Project:                    Asterisk
Issue ID:                   12432
Category:                   Channels/chan_gtalk
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 114095 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-14-2008 01:17 CDT
Last Modified:              04-16-2008 14:15 CDT
====================================================================== 
Summary:                    Gtalk channel allocation fails after large number of
buddy
Description: 
I am running asterisk from latest trunk (Asterisk SVN-trunk-r114093M)

Gtalk works fine as long as few buddies are present. As soon as number of
buddies goes up, Gtalk channel allocation starts failing when making new
Gtalk call

ERROR[4917]: chan_gtalk.c:908 gtalk_alloc: no gtalk capable clients to
talk to.

I can see that Gtalk client is online, and jabber messages are flowing. I
can even enter text from the Gtalk client and see that it is received by
asterisk. Hence Gtalk is connected but no calls go through. 

System is not out of resource and asterisk is only taking few tens MB of
RAM and ample of RAM is available

As I mentioned, Gtalk call works fine if number of buddies are less and
hence I do not see this as a setup issue. 


====================================================================== 

---------------------------------------------------------------------- 
 visu - 04-16-08 14:15  
---------------------------------------------------------------------- 
Hi Phsultan,

As I can see, on loaded system, when client logs out, it still maintain
the resources. While on non loaded system, the resources become none and it
works fine. 

So when client login again, loaded system now has two resources (old and
new). So when during finding the roster ID, first one which is not valid
gets picked up and call never goes through.

I yet to understand why call fails on loaded system when there is single
resources

Let me know if more information required.

Thanks 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-16-08 14:15  visu           Note Added: 0085575                          
======================================================================