[cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Haas, Neal nhaas at co.fresno.ca.us
Tue Nov 2 11:46:10 EDT 2010


FYI; I did the changes below, we still have it installed in a half dozen boxes, well it started to work again!! I will test it out for a couple of days to see if this was the only issue. But right now it looks as if it was…

“I managed to route calls from OCS by changing call classification on my OCS Trunk to off-net and changing the MTP Preferred Originating Codec to 711alaw. Thanks for all the help, hopefully this info will be useful in the future.”


Neal Haas

1020 S 10th St
Fresno, CA  93702
Desk 559.600.5890

From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Tuesday, November 02, 2010 8:29 AM
To: Sechaba Mokoena
Cc: Haas, Neal; Bill; Ahmed Elnagar; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

I meant the OS regional setting.  It will normally negotiate codecs, but not between alaw and ulaw that I am aware of.

From: Sechaba Mokoena [mailto:sechabam at gmail.com]
Sent: Tuesday, November 02, 2010 11:20 AM
To: Matt Slaga (US)
Cc: Haas, Neal; Bill; Ahmed Elnagar; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Hi Matt,

I'm not too sure about the regional template on OCS. I was told OCS would negotiate the codec with UCM by the Microsoft engineers, not too sure how true that is.
Kind regards,

Sechaba Mokoena



On 02 Nov 2010, at 2:49 PM, "Matt Slaga (US)" <Matt.Slaga at us.didata.com<mailto:Matt.Slaga at us.didata.com>> wrote:
The ‘offnet’ setting will only set the call origination setting inside of UCM.  The real fix is the MTP codec change.  Just out of curiosity, what regional template is applied to the OCS server?  I’m wondering if the regional template sets the ulaw/alaw default.

From: Sechaba Mokoena [mailto:sechabam at gmail.com]
Sent: Tuesday, November 02, 2010 4:00 AM
To: Haas, Neal
Cc: Bill; Matt Slaga (US); Ahmed Elnagar; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Hi all,

I managed to route calls from OCS by changing call classification on my OCS Trunk to off-net and changing the MTP Preferred Originating Codec to 711alaw. Thanks for all the help, hopefully this info will be useful in the future.
Kind regards,

Sechaba Mokoena



On 01 Nov 2010, at 5:21 PM, "Haas, Neal" <nhaas at co.fresno.ca.us<mailto:nhaas at co.fresno.ca.us>> wrote:
We had the Mediation server all working, make a SIP trunk to it (sorry lost or deleted my reference URL). We had the biggest issues, the thing would just stop working. We could make calls, receive calls, then it would just stop working. After a day or so it would start to work again and after a few calls it would stop excepting new calls.

Cisco pointed at Microsoft, Microsoft pointed at cisco. Even had Microsoft fly down to work on it………Finally just took it all out. Either go all Microsoft or go all cisco. They really are competing products

Neal

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill
Sent: Monday, November 01, 2010 7:47 AM
To: 'Matt Slaga (US)'; 'Ahmed Elnagar'; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

According to what I am told by the MS Rep it will do “pass through” or something similar so you don’t need the mediation server anymore. If you have remote sites that have a mix of the MOC client and IP phones you do not need a mediation server local to the site anymore and the media is direct between the end points.

________________________________
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Monday, November 01, 2010 9:45 AM
To: Bill; 'Ahmed Elnagar'; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Not with OCS.  The media path will never be directly from the IP phone to a MOC client directly.  It will always traverse the Mediation Server.  What it will do, however, is in certain cases G711 will pass through un-transcoded.  You can see this in mediation server traces and client traces.



From: Bill [mailto:bill at hitechconnection.net]
Sent: Monday, November 01, 2010 10:38 AM
To: Matt Slaga (US); 'Ahmed Elnagar'; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Yes but I don’t think the voice terminates on the mediation server anymore. The RTP G.711 call is directly between the MOC client and the Cisco IP phone once the call is setup.

Before it was MOC RTaudio to the mediation server and G.711 IP phone to the mediation server.

________________________________
From: Matt Slaga (US) [mailto:Matt.Slaga at us.didata.com]
Sent: Monday, November 01, 2010 9:34 AM
To: Bill; 'Ahmed Elnagar'; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

You absolutely need a mediation server (although in Lync it is part of the front end now) to integrate to UCM.  The mediation server handles the signaling and converts not just the codec (if necessary, it can allow G711 passthrough), but also SIP or SIP/TLS to SIP/MTLS.

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill
Sent: Monday, November 01, 2010 10:18 AM
To: 'Ahmed Elnagar'; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

It’s what the Microsoft reps told us during our discussion on Lync / CUCM integration.

________________________________
From: Ahmed Elnagar [mailto:ahmed_elnagar at rayacorp.com]
Sent: Monday, November 01, 2010 9:19 AM
To: Bill; Sechaba Mokoena
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Yes it was a session for an intro to Lync…maybe I will review the recorded session again if you got the information from  a solid source “maybe I miss-understand something in the session”.

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 [cid:image001.jpg at 01CB799C.C8CA6EC0]

From: Bill [mailto:bill at hitechconnection.net]
Sent: Monday, November 01, 2010 4:13 PM
To: Ahmed Elnagar; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

What version are you talking about? 2010 / Lync can use G.711 without a mediation server.

________________________________
From: Ahmed Elnagar [mailto:ahmed_elnagar at rayacorp.com]
Sent: Monday, November 01, 2010 9:14 AM
To: Bill; Sechaba Mokoena
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

This is new to me really…I had the below statement from a MS consultant “their only supported codec is RT-Audio and you need a mediation server whenever you need to integrate OCS with the outside world!!!”

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 [cid:image001.jpg at 01CB799C.C8CA6EC0]

From: Bill [mailto:bill at hitechconnection.net]
Sent: Monday, November 01, 2010 3:52 PM
To: Ahmed Elnagar; 'Sechaba Mokoena'
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

The MOC clients can communicate using G.711 without the need of a mediation server but you have to configure them to do so.

________________________________
From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ahmed Elnagar
Sent: Monday, November 01, 2010 8:42 AM
To: Sechaba Mokoena
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

I think you will need a MS mediation server “as per Microsoft design” in order to convert their codec “RT-Audio” to a codec that Cisco infrastructure can understand.

 Best Regards;
  Ahmed Elnagar
  Senior Network PS Engineer
  Mob: +2019-0016211
  CCIE#24697 (Voice)
 [cid:image001.jpg at 01CB799C.C8CA6EC0]

From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Sechaba Mokoena
Sent: Monday, November 01, 2010 3:11 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] Outbound Calls from OCS to Cisco IP Phone

Hi,

We're in the middle of a Microsoft OCS POC integrated with UCM 8.0. I can make internal and external calls from OCS using UCM as my gateway, but calls are dropped as soon as they're answered. Has anyone out there come across a similar problem.

Kind regards,

Sechaba Mokoena

Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.

Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.

Disclaimer: NOTICE The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Raya will not be liable for direct, special, indirect or consequential damages arising from alteration of the contents of this message by a third party or as a result of any malicious code or virus being passed on. Views expressed in this communication are not necessarily those of Raya.If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and return and/or destroy the original message.
________________________________

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.

________________________________

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.

________________________________

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.

________________________________

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101102/6f66d9b6/attachment.html>


More information about the cisco-voip mailing list