No subject

‘suggest’ it but if it’s the only option and it is not followed by
the remote peer the connect attempt should be rejected. A nice way to force
by suggesting :-)

At least is seems to me that it is what happens with for example IAX
clients.
When I have a configuration like this on my iax.conf :
disallow=all
allow=gsm
...

And when my remote client do not have GSM as one of the possible codecs,
the connect attempt is rejected and I receive the following message in my
zoiper iax client : “bearercapability notavail”

And on the asterisk server side I have the following message:
[Aug 30 11:40:50] NOTICE[1358]: chan_iax2.c:7645 socket_process: Rejected
connect attempt from XX.XX.XX.XX, requested/capability 0x200/0x60c
incompatible with our capability 0xe002.

Isn’t it suppose to work the same way with the gtalk ?
If the gtalk client doesn’t support one codec type (for example GSM) and
I have in gtalk.conf the:
disallow=all
allow=gsm

the connection shouldn’t be established also.
What do you think ?

This possible issue is related with establishing or not the connections
based on the peers capabilities (and asterisk server options).
But as you requested I will try also to test different codec options to
see if I can help in any way with the existing gtalk-asterisk codec
problems you pointed out. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-30-07 06:53  keepitcool     Note Added: 0069690                          
======================================================================