<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>SME is not meant to replace CUBE. SME is Cisco's reply to Kamailio (former OpenSER) and other centralized SIP routers. In the big SIP world, large SIP clients / providers typically have a SIP routing engine sitting in the center of their network. It is SIP's "Gatekeeper" equivalent and messaging mediator for all SIP call agents to include IP PBX and SBCs (CUBEs in Cisco world). RTP will not pass through it, only SIP messaging. What it does is presents a familiar GUI and way of doing things. If you have the ability to did deep into the SIP protocol and build a server on Solaris or LINUX, Kamailio is at least 100x more powerful and flexible. If you are not LINUX or Solaris smart and are not a SIP protocol level guy or gal, SME is most definitely a better path to take for centralized SIP CAC, message normalization, call
reporting, and troubleshooting. If this is SP level deployment, there are a ton of Kamailio programs who can come in a set it all up. </DIV>
<DIV> </DIV>
<DIV>What I would like to know, Is will this support the generation of early offer messaging without <SPAN>MTP</SPAN> support? This is feature is keeping Cisco out of the big SIP world. I know this is on the road map, but how late to the party will they show? </DIV>
<DIV> </DIV>
<DIV><BR>--- On <B>Sat, 5/15/10, Nick Matthews <I><matthnick@gmail.com></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="BORDER-LEFT: rgb(16,16,255) 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px"><BR>From: Nick Matthews <matthnick@gmail.com><BR>Subject: Re: [<SPAN>cisco</SPAN>-voip] Cisco SME<BR>To: "Ahmed Elnagar" <ahmed_elnagar@rayacorp.com><BR>Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><BR>Date: Saturday, May 15, 2010, 5:28 PM<BR><BR>
<DIV id=yiv441292078>CUBE = external<BR><BR>SME = internal<BR><BR>So even if you use SME to aggregate your internal dial plan and want to hook it up to a SIP trunk, you would still use a CUBE in front of your SME. SME is designed for larger deployments where dial plan aggregation is important. To a degree you can aggregate a dial plan on CUBE as well, but it is not as scalable or easy to manage. <BR><BR>To further confuse you, the following products can all do some sort of dial plan aggregation: CUSP, SIP proxy on CUPS, CUCM, SME, CUBE, and GK. <BR><BR><BR>-nick<BR><BR>
<DIV class=gmail_quote>On Sat, May 15, 2010 at 8:08 AM, Ahmed Elnagar <SPAN dir=ltr><<A href="http://us.mc504.mail.yahoo.com/mc/compose?to=ahmed_elnagar@rayacorp.com" rel=nofollow target=_blank ymailto="mailto:ahmed_elnagar@rayacorp.com">ahmed_elnagar@rayacorp.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex" class=gmail_quote>
<DIV lang=EN-US>
<DIV>
<P class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 11pt">So what it is the difference between it and CUBE…and when to use it and not use CUBE!!!</SPAN></DIV>
<DIV class=im>
<P class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 11pt"> </SPAN></DIV>
<DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10pt"> </SPAN><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt">Best Regards;</SPAN></DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> Ahmed Elnagar</SPAN></DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> Senior Network PS Engineer</SPAN></DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> Mob: +2019-0016211</SPAN></DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> CCIE#24697 (Voice)</SPAN></DIV>
<P style="BACKGROUND: white" class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 10.5pt"> <IMG alt=ccie_voice_large.gif width=63 height=63><IMG alt=ccvp_voice_large.gif width=63 height=63></SPAN></DIV></DIV>
<P class=MsoNormal><SPAN style="COLOR: rgb(31,73,125); FONT-SIZE: 11pt"> </SPAN></DIV></DIV>
<DIV style="BORDER-BOTTOM: rgb(181,196,223); BORDER-LEFT: rgb(181,196,223); PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: rgb(181,196,223) 1pt solid; BORDER-RIGHT: rgb(181,196,223); PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt"> <A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net" rel=nofollow target=_blank ymailto="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A> [mailto:<A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net" rel=nofollow target=_blank ymailto="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>] <B>On Behalf Of </B>Aman Chugh<BR><B>Sent:</B> Saturday, May 15, 2010 8:38 AM<BR><B>To:</B> Bill<BR><B>Cc:</B> cisco-voip voyp list<BR><B>Subject:</B> Re: [cisco-voip] Cisco SME</SPAN></DIV></DIV>
<DIV>
<DIV></DIV>
<DIV class=h5>
<P class=MsoNormal> </DIV>
<DIV>
<P class=MsoNormal>Check with your Cisco SE. It does offer some enchancements on trunking and yes it does not have phones registered on it.</DIV></DIV>
<DIV>
<P class=MsoNormal> </DIV></DIV>
<DIV>
<P class=MsoNormal><A href="http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs" rel=nofollow target=_blank>http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs</A></DIV></DIV>
<DIV>
<P class=MsoNormal> </DIV></DIV>
<DIV>
<P class=MsoNormal>Regards,</DIV></DIV>
<DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal>Aman</DIV></DIV>
<DIV>
<P class=MsoNormal>On Fri, May 14, 2010 at 9:15 PM, Matthew Saskin <<A href="http://us.mc504.mail.yahoo.com/mc/compose?to=msaskin@gmail.com" rel=nofollow target=_blank ymailto="mailto:msaskin@gmail.com">msaskin@gmail.com</A>> wrote:</DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal>It's basically just CUCM without IP phones registered. You use it as a point of centralized call routing (multiple CUCM clusters trunk to it, traditional PBX's via a gateway trunk to it, etc.). IME can be deployed centrally off of SME or off of a single CUCM 8 cluster.<BR><BR clear=all>Matthew Saskin<BR><A href="http://us.mc504.mail.yahoo.com/mc/compose?to=msaskin@gmail.com" rel=nofollow target=_blank ymailto="mailto:msaskin@gmail.com">msaskin@gmail.com</A><BR>203-253-9571<BR><BR>July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run<BR>Please support the Leukemia & Lyphoma Society<BR><A href="http://pages.teamintraining.org/nyc/nyctri10/msaskin" rel=nofollow target=_blank>http://pages.teamintraining.org/nyc/nyctri10/msaskin</A><BR><BR></DIV>
<DIV>
<DIV>
<P class=MsoNormal>On Fri, May 14, 2010 at 10:44 AM, Bill <<A href="http://us.mc504.mail.yahoo.com/mc/compose?to=bill@hitechconnection.net" rel=nofollow target=_blank ymailto="mailto:bill@hitechconnection.net">bill@hitechconnection.net</A>> wrote:</DIV></DIV>
<BLOCKQUOTE style="BORDER-BOTTOM: rgb(204,204,204); BORDER-LEFT: rgb(204,204,204) 1pt solid; PADDING-BOTTOM: 0in; PADDING-LEFT: 6pt; PADDING-RIGHT: 0in; MARGIN-LEFT: 4.8pt; BORDER-TOP: rgb(204,204,204); MARGIN-RIGHT: 0in; BORDER-RIGHT: rgb(204,204,204); PADDING-TOP: 0in">
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt">So I am looking at the Session Manager Edition. Is it just CUCM but without IP phones registered to it? Is it just a centralized call manager for centralized call managers? Also if we deploy IME at some point do we need SME or can we just use the CUCM cluster we already have? </SPAN></DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt"> </SPAN></DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt"> </SPAN></DIV>
<P class=MsoNormal> </DIV></DIV></DIV>
<P class=MsoNormal> </DIV></DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal>_______________________________________________<BR>cisco-voip mailing list<BR><A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" rel=nofollow target=_blank ymailto="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel=nofollow target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A></DIV></BLOCKQUOTE></DIV>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><BR><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" rel=nofollow target=_blank ymailto="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel=nofollow target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A></DIV></DIV>
<P class=MsoNormal> </DIV></DIV></DIV></DIV>
<DIV> </DIV>
<DIV class=im>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. </DIV></DIV><BR>_______________________________________________<BR>cisco-voip mailing list<BR><A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net"
rel=nofollow target=_blank ymailto="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel=nofollow target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR></BLOCKQUOTE></DIV><BR></DIV><BR>-----Inline Attachment Follows-----<BR><BR>
<DIV class=plainMail>_______________________________________________<BR>cisco-voip mailing list<BR><A href="http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net" ymailto="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A href="https://puck.nether.net/mailman/listinfo/cisco-voip" target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></DIV></BLOCKQUOTE></td></tr></table><br>