[prev in list] [next in list] [prev in thread] [next in thread]
List: asterisk-bugs
Subject: [asterisk-bugs] [Asterisk 0010604]: Codec options in gtalk.conf not
From: noreply () carolina ! digium ! com
Date: 2008-03-31 11:59:08
Message-ID: 9f43490b9358368725d105fa67e9c3e8 () bugs ! digium ! com
[Download RAW message or body]
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=10604
======================================================================
Reported By: keepitcool
Assigned To: phsultan
======================================================================
Project: Asterisk
Issue ID: 10604
Category: Channels/chan_gtalk
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.11
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 08-30-2007 08:00 CDT
Last Modified: 03-31-2008 06:59 CDT
======================================================================
Summary: Codec options in gtalk.conf not respected
Description:
When you have in gtalk.conf the following configuration:
[buddy]
disallow=all
allow=gsm
...
The gtalk connection is established even if the gtalk client do not
support the GSM codec, and the connection/channel appears established with
a different codec that it is not allowed (like for example the slin
codec).
On the other side, a similar configuration with IAX works as it is
supposed to.
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 ?
Testing components:
- Fedora core 3 + Asterisk server 1.4.11 (no zaptel, no libpri) + iksemel
1.3
- Google Talk client 1.0.0.104
- With the following patchs applied:
http://bugs.digium.com/view.php?id=10509
http://bugs.digium.com/view.php?id=10548 (branch-1.4-10548-3.diff)
======================================================================
----------------------------------------------------------------------
phsultan - 03-31-08 06:59
----------------------------------------------------------------------
Yep, I'll work back on this one.
Issue History
Date Modified Username Field Change
======================================================================
03-31-08 06:59 phsultan Note Added: 0084774
======================================================================
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-bugs mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic