<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>I think our developer writing a app found a workaround other than using a GUID with SIP CVP. But I did some more Bing searches, however I think it’s a dead issue currently.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Seems SIP protocol hasn’t standardized GUID, drafts expired. Some searches on GUID also reference the other term Universally Unique Identifier (UUID) which is the same concept different name.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>Nothing about GUIDs in Asterisk either.<o:p></o:p></p><p class=MsoNormal><span style='color:#1F497D'><a href="http://cdn.oreilly.com/books/9780596510480.pdf">http://cdn.oreilly.com/books/9780596510480.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Apparently the SIP GUID expired without approval with the sponsor being Nortel which is no longer in business!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="https://datatracker.ietf.org/doc/draft-stucker-sip-guid/">https://datatracker.ietf.org/doc/draft-stucker-sip-guid/</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Some GUID references<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="http://docwiki.cisco.com/wiki/Call_Tracing:_What_components_did_the_call_reach%3F">http://docwiki.cisco.com/wiki/Call_Tracing:_What_components_did_the_call_reach%3F</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Voice XML Programmers Guide<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>cisco-guid<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>cisco-newguid<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>session.telephone.com.cisco.guid<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="http://www.cisco.com/en/US/docs/ios/voice/vxml/developer/guide/vxmlpg.pdf">http://www.cisco.com/en/US/docs/ios/voice/vxml/developer/guide/vxmlpg.pdf</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Wes Sisk [mailto:wsisk@cisco.com] <br><b>Sent:</b> Friday, May 06, 2011 11:02 AM<br><b>To:</b> Jason Aarons (AM)<br><b>Cc:</b> cisco-voip (cisco-voip@puck.nether.net)<br><b>Subject:</b> Re: [cisco-voip] Anyone famliar with GUIDs in CallManager/VXML?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Jason,<br><br>Can you elaborate a bit more?<br><br>My initial interpretation of your post reminds me of a commonly discussed feature for Cisco UC called "global call id's". The idea there is to generate a single GUID to track a call through all products and features. This requires passing the GUID in signaling (h323, SIP, SCCP, MGCP). The concept garners significant interest. Implementation complexity has been prohibitive so far.<br><br>This suggests a possibility - the "GUID" referenced may be the h.323 GUID assigned per-call when h.323 is used. CVP may have exposed that in original H.323 integrations. SIP does not have a GUID concept AFAIK - we ran into this with Analysis Manager (see below). So if you are using SIP integration there would be no h.323 GUID. Unless someone took special steps to translate something from signaling into a GUID there would be no SIP GUID per say.<br><br><br>The closest that exists today is Analysis Manager:<br><a href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_1/rtmt/ch1_overview.html">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_1/rtmt/ch1_overview.html</a> <br>This pulls CDRs from CUCM, IPCC, Unity?, and IOS? and uses unique attributes of signaling (tcp port numbers, h323 guids, sccp call ref numbers, SIP call ref numbers, ...). I'm not clear of the products covered in the current release. All of those were in the original feature discussion.<br><br>Regards,<br>Wes<br><br>On 5/6/2011 10:42 AM, Jason Aarons (AM) wrote: <o:p></o:p></p><p class=MsoNormal>From a co-worker doing some UCCE work “I’m not getting GUID on any of my CVP calls that originate from UCM. Both calls from the dialer 30VIP ports and calls to CTI RPs don’t have a guid”<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>I wasn’t familiar that CallManager used GUIDs for call tracking. Anyone familiar with a setting to turn GUIDs on or off? -jason<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=1 width="100%" align=center></span></div><p><strong><span style='font-size:10.0pt;color:gray'>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </span></strong><o:p></o:p></p><pre><span style='color:gray'><o:p> </o:p></span></pre><pre><span style='color:gray'><o:p> </o:p></span></pre><pre><span style='color:gray'>_______________________________________________<o:p></o:p></span></pre><pre><span style='color:gray'>cisco-voip mailing list<o:p></o:p></span></pre><pre><span style='color:gray'><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></span></pre><pre><span style='color:gray'><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></pre></div></body></html>