<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18928"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV><SPAN class=015143414-07102010><FONT size=2
face=Arial>Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=015143414-07102010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=015143414-07102010><FONT size=2 face=Arial>We are a Cisco
Partner and we managed to do that. No bragging but it truly was a significant
headache to track such types of calls. Off-net to Offnet call rating and
billing is one of the hardest to track alright. I suggest that you inspect
CallLegs and LastRedirectNumber fields in the CDR.</FONT></SPAN></DIV>
<DIV><SPAN class=015143414-07102010><FONT size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=015143414-07102010><FONT size=2
face=Arial>BR</FONT></SPAN></DIV>
<DIV>
<HR tabIndex=-1>
</DIV>
<DIV><FONT size=2 face=Tahoma><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Wes
Sisk<BR><B>Sent:</B> Wednesday, 6 October 2010 3:33 PM<BR><B>To:</B>
sashank<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] CDR and billing questions<BR></FONT><BR></DIV>
<DIV></DIV>You can follow the transfer in CDRs to identify the original leg and
the consult leg. It is possible and done. Kudos to the CDR billing
partners who work through the logic to make it
happen.<BR><BR>/wes<BR><BR>sashank wrote:
<BLOCKQUOTE
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-LEFT: 0px !important; PADDING-RIGHT: 0px !important; MARGIN-LEFT: 0px !important; BORDER-TOP: medium none; MARGIN-RIGHT: 0px !important; BORDER-RIGHT: medium none"
cite=mid:000001cb6511$cf0dab20$6d290160$@pathi@locuz.com type="cite">
<META name=Generator content="Microsoft Word 12 (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-face {
font-family: Helvetica;
}
@font-face {
font-family: Helvetica;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Consolas;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: Lucida Grande;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.apple-style-span {
mso-style-name: apple-style-span
}
SPAN.apple-converted-space {
mso-style-name: apple-converted-space
}
SPAN.EmailStyle19 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</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]-->
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: rgb(31,73,125); FONT-SIZE: 11pt">What
happens if the c alls are transferred to auto attendant on unity connection. A
call comes from outside and the welcome prompt comes up and if the user will
dial an internal extension the call will be routed to the extension. Here is
the thing, when you see the CDR’s fpr incoming calls, the it shows that all
the incoming calls are routed to the auto attendant pilot number, even if they
dial the internal extension. So I don’t think that any work around is there
for this.<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">Warm
Regards,<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">Venkata
Sasanka.pathi(-91 950 265 2290)<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">Consultant
| unified communications<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">Locuz
Enterprise Solutions Ltd. (A Subsidiary of 3i-Infotech)<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">(office:914066115656)<O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> <A
href="mailto:sasanka.pathi@locuz.com" moz-do-not-send="true"><SPAN
style="COLOR: blue">sasanka.pathi@locuz.com</SPAN></A><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"><A
href="http://www.locuz.com" moz-do-not-send="true"><SPAN
style="COLOR: blue">www.locuz.com</SPAN></A><O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: rgb(31,73,125); FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> <A
class=moz-txt-link-abbreviated
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
[<A class=moz-txt-link-freetext
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</A>]
<B>On Behalf Of </B>Ryan Ratliff<BR><B>Sent:</B> Tuesday, October 05, 2010
8:05 PM<BR><B>To:</B> Lelio Fulgenzi<BR><B>Cc:</B> <A
class=moz-txt-link-abbreviated
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><B>Subject:</B>
Re: [cisco-voip] CDR and billing questions<O:P></O:P></SPAN></P></DIV></DIV>
<P class=MsoNormal><O:P></O:P></P>
<P class=MsoNormal>The information is all there in the CDR records it's up to
the 3rd party to use it.<O:P></O:P></P>
<DIV>
<P class=MsoNormal><A
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_2/cdrdef/cdrex.html#wp1245778"
moz-do-not-send="true">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/8_0_2/cdrdef/cdrex.html#wp1245778</A><O:P></O:P></P></DIV>
<DIV>
<P class=MsoNormal><O:P></O:P></P>
<DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Helvetica','sans-serif'">-Ryan<O:P></O:P></SPAN></P></DIV></DIV>
<P class=MsoNormal><O:P></O:P></P>
<DIV>
<DIV>
<P class=MsoNormal>On Oct 5, 2010, at 10:01 AM, Lelio Fulgenzi
wrote:<O:P></O:P></P></DIV>
<P class=MsoNormal><BR><BR><SPAN class=apple-style-span><SPAN
style="FONT-FAMILY: 'Lucida Grande','serif'; FONT-SIZE: 13.5pt"><O:P></O:P></SPAN></SPAN></P>
<DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">I
would be interested in hearing about this as well.<BR><BR>I also believe that
transfers to internal parties behave the same way.<BR><BR>For example:
Extension A calls an offnet long distance number then transfers to extension B
after 1 minute.<BR><BR>In this case, your CDR will only show a 1 minute LD
call from extension A. I _think_ the CDR will show the transfer as a call from
the LD number to extension B which doesn't show up as a billable
call.<BR><BR>I believe some CDR processing companies can catch this by using
the call leg identifiers, but it's not easy.<BR><BR>---<BR>Lelio Fulgenzi,
B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G
2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Cooking
with unix is easy. You just sed it and forget it.<SPAN
class=apple-converted-space> </SPAN><BR>
-
LFJ (with apologies to Mr. Popeil)<BR><BR></SPAN><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><O:P></O:P></SPAN></P>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">
<HR id=zwchr align=center SIZE=2 width="100%">
</SPAN></DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">From:<SPAN
class=apple-converted-space> </SPAN></SPAN></B><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt">"Sandy
Lee" <<A href="mailto:Sandy.Lee@dti.ulaval.ca"
moz-do-not-send="true">Sandy.Lee@dti.ulaval.ca</A>><BR><B>To:<SPAN
class=apple-converted-space> </SPAN></B><A
href="mailto:cisco-voip@puck.nether.net"
moz-do-not-send="true">cisco-voip@puck.nether.net</A><BR><B>Sent:<SPAN
class=apple-converted-space> </SPAN></B>Tuesday, October 5, 2010 9:55:59
AM<BR><B>Subject:<SPAN
class=apple-converted-space> </SPAN></B>[cisco-voip] CDR and billing
questions<O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"
lang=FR>Hi everyone,</SPAN><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"
lang=FR></SPAN><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">In
UCM 7.1(5) we’re not able to identify from which extension the call was made
when it’s a transfer between external parties. For example, I receive an
external call from (A) and I transfer/conference with another external LD
number (B). The call from A to B appears in the CDR, but there is no way our
billing app can “match” with my extension, so the billing app can’t bill back
my extension for the call. Is there a parameter somewhere to solve this
issue?<O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">In
CUCM 4.1(3) we couldn’t do it either but we could live with it because we
didn’t have a lot of those. We have a legacy PBX and from its CDR, the billing
app can do it. Until this summer, our main number was going through the legacy
PBX, so we could match the DNs. But now, our main number has been transferred
on the IP telephony side and we have to be able to bill
back.<O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">I
can’t block offnet to offnet transfers, this is not an option for
me.<O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt">Thanks
for any input on this.<O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 10pt">Sandy.</SPAN><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><O:P></O:P></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Verdana','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A href="mailto:cisco-voip@puck.nether.net"
moz-do-not-send="true">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-voip</A><O:P></O:P></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Lucida Grande','serif'; FONT-SIZE: 13.5pt">_______________________________________________<BR>cisco-voip
mailing list<BR><A href="mailto:cisco-voip@puck.nether.net"
moz-do-not-send="true">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-voip</A><O:P></O:P></SPAN></P></DIV></DIV>
<P class=MsoNormal><O:P></O:P></P></DIV></DIV><PRE wrap=""><HR SIZE=4 width="90%">
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE></BODY></HTML>