[cisco-voip] MediaSense Configuration

Thu Feb 26 12:26:28 EST 2015

CSR 15 will read your mind and pick the route group(s) you meant to add to
your route list(s).

On Thu, Feb 26, 2015 at 11:22 AM Matthew Loraditch <
MLoraditch at heliontechnologies.com> wrote:

>  I figured it out… you kinda need to add your route group to your route
> list….
>
>
>
> Doh!
>
>
>
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
> Network Engineer
> Direct Voice: 443.541.1518
>
>  Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter
> <https://twitter.com/HelionTech> | LinkedIn
> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> |
> G+ <https://plus.google.com/+Heliontechnologies/posts>
>
>
>
> *From:* Chris Ward (chrward) [mailto:chrward at cisco.com]
> *Sent:* Thursday, February 26, 2015 11:54 AM
> *To:* Bill Talley; Matthew Loraditch
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] MediaSense Configuration
>
>
>
> What happens when you call the number you put in the recording profile? It
> should answer and record. You won’t see or hear anything. If you get a busy
> or reorder tone, your routing is not setup correctly.
>
>
>
> +Chris
>
> TME - MediaSense and Unity Connection
>
>
>
> *From:* Bill Talley [mailto:btalley at gmail.com <btalley at gmail.com>]
> *Sent:* Wednesday, February 25, 2015 6:29 PM
> *To:* Matthew Loraditch
> *Cc:* Chris Ward (chrward); cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] MediaSense Configuration
>
>
>
> It should answer.
>
>
>
> On Wed, Feb 25, 2015 at 5:15 PM, Matthew Loraditch <
> MLoraditch at heliontechnologies.com> wrote:
>
>  It is forced on, on my test phone, albeit we have it on system wide as
> well. I've just been trying to eliminate things.
>
> Should the route pattern I have for the mediasense server ring busy if I
> dial it? I have another recording solution where the number answers in a
> similar setup.
>
>
>
> Matthew G. Loraditch - CCNP-V, CCNA-R&S, CCDA
> Network Engineer
>
>
>
> We *understand *and *solve *your
>
> technology challenges so
>
> you can sell and service cars.
>
>
>
> Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter
> <https://twitter.com/HelionTech> | LinkedIn
> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> |
> G+ <https://plus.google.com/+Heliontechnologies/posts>
>     ------------------------------
>
> *From:* Chris Ward (chrward) [chrward at cisco.com]
> *Sent:* Wednesday, February 25, 2015 5:48 PM
> *To:* Matthew Loraditch; Bill Talley
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* RE: [cisco-voip] MediaSense Configuration
>
> Also, make sure the BiB on the phones are enabled. Its disabled by
> default. You need to do it per device or in the CCM service parameter.
>
>
>
> +Chris
>
> TME - MediaSense and Unity Connection
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Matthew Loraditch
> *Sent:* Wednesday, February 25, 2015 3:54 PM
> *To:* Bill Talley
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] MediaSense Configuration
>
>
>
> Ok that’s what I did and what I thought. Time to dig!
>
>
>
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
> Network Engineer
> Direct Voice: 443.541.1518
>
> Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter
> <https://twitter.com/HelionTech> | LinkedIn
> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> |
> G+ <https://plus.google.com/+Heliontechnologies/posts>
>
>
>
> *From:* Bill Talley [mailto:btalley at gmail.com <btalley at gmail.com>]
> *Sent:* Wednesday, February 25, 2015 3:46 PM
> *To:* Matthew Loraditch
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] MediaSense Configuration
>
>
>
> doh...
>
> "Make you set the source to phone preferred AND NOT gateway preferred
> (assuming you are using the BIB)."
>
>
>
> On Wed, Feb 25, 2015 at 2:44 PM, Bill Talley <btalley at gmail.com> wrote:
>
>  Correct on licensing.  Just went through this myself and it was really
> easy to setup to record forked audio.  The only issue we ran into relates
> to securing of the recording files.  With stand alone MediaSense, users who
> need access to the recordings are added as API users in MS and have access
> to ALL recordings, not just the recordings they are a party in.
>
> In CUCM you'll create a SIP trunk to MediaSense, create route pattern
> pointing to the trunk, create a recording profile with a DN to match the
> route pattern.  Then enable the BIB on the phone device and under the DN
> set the recording profile, recordig option and recording source on the
> phone.  Make you set the source to phone preferred gateway preferred
> (assuming you are using the BIB).
>
>
>
> On Wed, Feb 25, 2015 at 2:22 PM, Matthew Loraditch <
> MLoraditch at heliontechnologies.com> wrote:
>
>   Trying to setup a PoC for media sense internally to validate I can
> deploy at a client for recording purposes… from what I can tell licensing
> is honor based?
>
> Secondly from what I am reading this section of the documentation is all I
> have to do:
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/mediasense/105_SU1/User_Guide/CUMS_BK_M5B01864_00_ms-user-guide-105-SU1/CUMS_BK_M5B01864_00_ms-user-guide-105_chapter_010.html#CUMS_TP_M28EF01E_00
>
> Fork calls into media sense? The default rule in MS says record all audio
>
>
>
> Is there anything else I need to do? Trying now to figure out what logs to
> look at to see if it’s actually seeing anything or not, because nothing
> shows up on the system.
>
>
>
>
>
> Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
> Network Engineer
> Direct Voice: 443.541.1518
>
> Facebook <https://www.facebook.com/heliontech?ref=hl> | Twitter
> <https://twitter.com/HelionTech> | LinkedIn
> <https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> |
> G+ <https://plus.google.com/+Heliontechnologies/posts>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
>
>
>  _______________________________________________
> cisco-voip mailing list
> 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/20150226/7ac0e74b/attachment.html>