[cisco-voip] reporting in CUCM

[Brian Meade (brmeade)]

Lelio,

The way I usually do that is by building a SIP Trunk and just pointing it back to the same CUCM node to form the loop.  It scales a bit better and requires no additional hardware.

Brian

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Tuesday, February 25, 2014 10:10 AM
To: Brian Meade (brmeade)
Cc: Cisco VOIP; Shaihan Jaffrey
Subject: Re: [cisco-voip] reporting in CUCM

Something I've considered (theorized) is using a couple of T1 ports and a cross-connect cable and specialized partitions and calling search spaces in order to implement FACs/CMCs to on-net destinations. You're limited to the 23 channels, but it should suffice.

I'm not sure if this helps you or not, but it's an idea.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
To: "Shaihan Jaffrey" <schaehan at gmail.com<mailto:schaehan at gmail.com>>
Cc: "Cisco VOIP" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Tuesday, February 25, 2014 9:54:06 AM
Subject: Re: [cisco-voip] reporting in CUCM
Shaihan,

Unfortunately the built-in CMC functionality only allows CMCs on route patterns which limits you to just outbound calls.

There are 3rd party products that extend this functionality to inbound calls.

One of these products is CallLog Premium- https://marketplace.cisco.com/catalog/products/3841

Thanks,
Brian
From: Shaihan Jaffrey [mailto:schaehan at gmail.com]
Sent: Tuesday, February 25, 2014 9:50 AM
To: Brian Meade (brmeade)
Cc: Cisco VOIP
Subject: Re: [cisco-voip] reporting in CUCM

HI Brian,
Will CMC work for inbound calls.

Regards.

On Mon, Feb 24, 2014 at 11:44 PM, Brian Meade (brmeade) <brmeade at cisco.com<mailto:brmeade at cisco.com>> wrote:
Shaihan,

Your first requirement will work with UCCX and making custom not-ready codes.

You can use Client Matter Codes in CUCM for your 2nd requirement.

Thanks,
Brian

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Shaihan Jaffrey
Sent: Monday, February 24, 2014 1:32 PM
To: Cisco VOIP
Subject: [cisco-voip] reporting in CUCM

Can we accomplish below points in cucm:

Reporting of users login / logout / tea break / prayer break / meeting break status (i.e. complete login-logout monthly report of each employee)

Marking special codes in CDR against the caller and called number. A number like 1111 for status related calls, 2222 for information related calls, 3333 for complain tracking related calls etc.

Regards.


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140225/7f5152b4/attachment.html>