[cisco-voip] Does anyone know the features sip phones do that have that SCCP phones can do?

[Mac GroupStudy]

Good points Wes with the exception being how a SIP phone sends digits. Only
the older A series phones (7940, 7960, etc.) do not support KPML (Key Pad
Markup Language). The newer phones do support KPML and therefore do not
require SIP Dial rules to be built. Also, for the SIP profile you can just
use the default unless you have specific change requirements (profiles tweak
the timers and such that SIP uses).

Mac

On Tue, Aug 31, 2010 at 2:53 PM, Wes Sisk <wsisk at cisco.com> wrote:

>  Hi Greg,
>
> One bite at a time. Inline, ws.
>
>
> Gregory Wenzel wrote:
>
> I have a client with approx 1000 phones and is about to do an office job on
> this legacy system. He is stuck on sip, why I have no clue
>
> ws: yep, hear this frequently. "We want SIP!"
>
>  but most likely he wants to use cucm8.5 with cheap sip phones
>
> ws: 3rd party SIP phones will have to provisioned by whatever means they
> offer.  With Cisco phones doing SIP we use vendor extensions so that SIP
> phone user experience is nearly seemless compared to SCCP phone user
> experience.  It is not yet possible to do all of the features in fully
> "standardized" (not really a standard) SIP.  For a start toward the details
> try the SIP line side messaging guide:
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/sip_msg/line_std/8_0_1/siplst801.pdf
>
>  besides his service provider telling him he should go all sip and run
> g729 on-net is not such a great advice, that will only save him in the
> shortrun with purchasing dsp modules. They have no bandwidth issue haveing a
> comcast tls 100mb link betw the two sites and a few satelite offices in the
> philly area. Not ever having built a purely sip system. They have 3 pri's
> now and I dont see them needing to run g729 onnet and  loose that sound
> quality.
>
> What does it mean when you have to build the dial plan?
>
> ws: SIP endpoints each need local instruction on what to do with digits.
> With Cisco CM and Cisco SIP phones phones default to 'send everything to the
> server' so the server still performs central routing.  You can get creative
> with routing at the endpoints similar to host based routing if you have an
> IP background. Normal conditions apply, just because you can doesn't mean
> you should.
>
>  and a sip profife for each phone?
>
> ws: yep, pretty much every phone gets a profile.  look for good bulk
> provisioning in the phones.
>
>  im embarassed to even ask that but wanted some clairfication from anyone
> on the group for the dial plan question and besides video advantage not
> working yet with sip phones what are the other features that do not work
> yet?
>
> ws: Now it feels like we've jumped back to Cisco CM + Cisco phones.  The
> last SIP/SCCP comparison I saw was here:
>
> Note, if you deploy Cisco CM + Cisco phones the SIP experience can be very
> similar to SCCP experience for both user and administrator.  However, this
> is only by vendor extension.  Cisco CM with "basic sip device" offers very
> basic features.  That said feature support varies even within Cisco phone
> models.  Check the Administration Guide for each model phone (or get your
> account team to compile?) to verify details. Example:
>
> http://www.cisco.com/en/US/customer/docs/voice_ip_comm/cuipph/7975G_7971g-ge_7970g_7965g_7945g/8_0/english/administration/guide/7970dif.html
>
> /Wes
>
>
> even a  link to the answer would help or a kick in the butt right direction
> would be great
>
>
> Regards,
>
> Greg
>
> ------------------------------
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttps://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/20100916/0859221e/attachment.html>