[asterisk-bugs] [Asterisk 0018799]: GTalk Channel Naming Deviates from TECH/name-SESSION
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Feb 11 22:11:10 CST 2011
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=18799
======================================================================
Reported By: vmikhelson
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18799
Category: Channels/chan_gtalk
Reproducibility: always
Severity: tweak
Priority: normal
Status: new
Asterisk Version: 1.8.2.3
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-02-11 22:11 CST
Last Modified: 2011-02-11 22:11 CST
======================================================================
Summary: GTalk Channel Naming Deviates from TECH/name-SESSION
Description:
Normally channels comply with the "TECH/name-SESSION" naming convention,
where:
TECH -- is technology, e.g. ZAP, SIP, DAHDI, GTALK, etc.
name -- name of the specific trunk instance
SESSION -- unique session ID
Gtalk works differently which may be related with its relationship to
Jabber (just a guess).
It would be nice if GTalk complied with the same naming convention as
other channels do. The existing deviation breaks some applications like FOP
which rely on the "known" channel name structure.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-02-11 22:11 vmikhelson New Issue
2011-02-11 22:11 vmikhelson Asterisk Version => 1.8.2.3
2011-02-11 22:11 vmikhelson Regression => No
2011-02-11 22:11 vmikhelson SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list