Summary:	ASTERISK-17395: GTalk Channel Naming Deviates from TECH/name-SESSION
Reporter:	Vladimir Mikhelson (vmikhelson)	Labels:
Date Opened:	2011-02-11 22:11:10.000-0600	Date Closed:	2011-02-16 15:25:03.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_gtalk
Versions:	1.8.2	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
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. ****** ADDITIONAL INFORMATION ****** Here is the example from the console log to illustrate.    -- Called GV8612/+1NXXNXXXXXX@voice.google.com    -- Gtalk/+1NXXNXXXXXX@voice.google.com-3648 is ringing    -- Gtalk/+1NXXNXXXXXX@voice.google.com-3648 answered DAHDI/7-1 The first line refers to the trunk specific string, "GV8612" Then the trunk name presented in the second and third lines is constructed as "TECH/<called URI>-SESSION
Comments:	By: Vladimir Mikhelson (vmikhelson) 2011-02-13 20:20:49.000-0600 There is one more deviation from standard. GTalk leaves CID number blank. It populates the CID name though. -Vladimir By: Leif Madsen (lmadsen) 2011-02-16 15:25:02.000-0600 This is a feature request without a supplied patch, which is not accepted on the issue tracker. Please feel free to reopen this issue if you're able to provide a patch for this issue. Alternatively you may use the mailing lists for support.