[cisco-voip] Cisco SME

[Nick Matthews]

SME is basically a specialized CUCM.  CUSP is a module that only does SIP
signaling and manipulation, routing, etc.

With SME you can still integrate things like a corporate directory, web
services, things like IME, SAF, etc.  It uses a GUI, has full monitoring and
SNMP support.

CUSP is just signaling - and even then normally just the INVITE and not any
mid-call signals that will go between the devices unless record route is
on.  It's basically a SIP gatekeeper, although it hasn't implemented
bandwidth limitations yet, nor does it process registrations.

-nick

On Mon, May 17, 2010 at 2:28 AM, Marty van de Veerdonk <
marty at voiceidentity.nl> wrote:

> But what is the difference then between SME and CUSP (SIP Proxy)?
> CUSP is also positioned as centralized SIP "gatekeeper".
>
>
> ----- Oorspronkelijk bericht -----
> Van: "ash AD" <commo_ssg_31f at yahoo.com>
>
> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
> Verzonden: Zondag 16 mei 2010 02:06:24
> Onderwerp: Re: [cisco-voip] Cisco SME
>
>
> 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.
>
> What I would like to know, Is will this support the generation of early
> offer messaging without MTP 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?
>
>
> --- On *Sat, 5/15/10, Nick Matthews <matthnick at gmail.com>* wrote:
>
>
> From: Nick Matthews <matthnick at gmail.com>
> Subject: Re: [cisco-voip] Cisco SME
> To: "Ahmed Elnagar" <ahmed_elnagar at rayacorp.com>
> Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net>
> Date: Saturday, May 15, 2010, 5:28 PM
>
> CUBE = external
>
> SME = internal
>
> 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.
>
> 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.
>
>
> -nick
>
> On Sat, May 15, 2010 at 8:08 AM, Ahmed Elnagar <ahmed_elnagar at rayacorp.com<http://us.mc504.mail.yahoo.com/mc/compose?to=ahmed_elnagar@rayacorp.com>
> > wrote:
>
>>  So what it is the difference between it and CUBE…and when to use it and
>> not use CUBE!!!
>>
>>
>>
>>  Best Regards;
>>
>>   Ahmed Elnagar
>>
>>   Senior Network PS Engineer
>>
>   Mob: +2019-0016211
>
>   CCIE#24697 (Voice)
>
>  [image: ccie_voice_large.gif][image: ccvp_voice_large.gif]
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net>[mailto:
> cisco-voip-bounces at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip-bounces@puck.nether.net>]
> *On Behalf Of *Aman Chugh
> *Sent:* Saturday, May 15, 2010 8:38 AM
> *To:* Bill
> *Cc:* cisco-voip voyp list
> *Subject:* Re: [cisco-voip] Cisco SME
>
>
>
> Check with your Cisco SE. It does offer some enchancements on trunking and
> yes it does not have phones registered on it.
>
>
>
>
> http://docwiki.cisco.com/wiki/Unified_Communications_Manager_-_Session_Manager_Edition:_Session_Manager_Designs
>
>
>
> Regards,
>
> Aman
>
> On Fri, May 14, 2010 at 9:15 PM, Matthew Saskin <msaskin at gmail.com<http://us.mc504.mail.yahoo.com/mc/compose?to=msaskin@gmail.com>>
> wrote:
>
> 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.
>
> Matthew Saskin
> msaskin at gmail.com<http://us.mc504.mail.yahoo.com/mc/compose?to=msaskin@gmail.com>
> 203-253-9571
>
> July 18, 2010 - 1500m swim (in the hudson), 40k bike, 10k run
> Please support the Leukemia & Lyphoma Society
> http://pages.teamintraining.org/nyc/nyctri10/msaskin
>
>  On Fri, May 14, 2010 at 10:44 AM, Bill <bill at hitechconnection.net<http://us.mc504.mail.yahoo.com/mc/compose?to=bill@hitechconnection.net>>
> wrote:
>
>   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?
>
>
>
>
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> 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.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<http://us.mc504.mail.yahoo.com/mc/compose?to=cisco-voip@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
>
> _______________________________________________
> 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/20100517/cab39f38/attachment.html>