[cisco-voip] Verify which device and firmware have sccp v 20 support

Tue Feb 21 15:59:31 EST 2012

Curious.... 

Is the documentation that Erik refers to, i.e. the one that states "SCCP v20", Cisco based documentation? Here's my two cents: 

    • if there is official Cisco documentation (including bugs) that list SCCP version numbers, the SCCP version number should probably be listed in the release notes for that firmware 
    • if there is disagreement whether to publish SCCP version support (which is OK, heck it's your product) there should not be any documentation that uses SCCP version as the only differentiator, i.e. if you wish to include it for reference, fine, but listing firmware versions that we have access to will be necessary 

that being said, if you really want to know what version of SCCP a firmware has, you can register it to an SRST host and during the registration process, I believe the SCCP version number is kicked out. not ideal, but you'll get some idea. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 

----- Original Message -----
From: "Jason Aarons (AM)" <jason.aarons at dimensiondata.com> 
To: "Erik Goppel" <egoppel at gmail.com>, "Wes Sisk" <wsisk at cisco.com>, cisco-voip at puck.nether.net 
Sent: Tuesday, February 21, 2012 3:51:55 PM 
Subject: Re: [cisco-voip] Verify which device and firmware have sccp v 20 support 

I think what Wes is saying is that SCCP v20 is not out yet, so your back to the current shipping Version 19. Is that correct Wes? 

Wonder if Version 20 means a ASA upgrade for SCCP inspection? 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erik Goppel 
Sent: Tuesday, February 21, 2012 3:40 PM 
To: Wes Sisk; cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] Verify which device and firmware have sccp v 20 support 

Wes, 

thanks for the feedback, but unfortunately it does not help me that much. 

The reason why i am asking is, i am currently working on a design, that requires the usage of a sip trunk with early-offer support. 

My end-customer does not want to use a CUBE (against my advice, but ok), so i needed to check some items regarding the earl-offer requirements. (as the sip provider offers sip trunks with early offer) 

As per Cisco documentation, it states that there is no MTP requirement for an early-offer sip trunk, when the call is initiated from the following devices: 

Cisco Unified Communications Manager supports early offer (without requiring MTP) when the call gets initiated from one of the following devices: 

•SIP phones 

•SCCP phones with SCCP v20 support (which provides media port information through the getPort capability) 

•MGCP gateways 

•Incoming H323 fast start calls 

•Incoming early offer SIP trunk calls 

Now to ensure my customer is using SCCP phones with SCCP version 20, i need to know which endpoints are capable of handling SCCP version 20. 

Also, i need to know in which firmware version this is enabled, so the deployment will be rolled-out with the correct version. 

If i do need to make use of the MTP`s (as far as i have researched, the need to be HW based MTP`s with IOS 15.1.(2)T) , my business case for the requirement of the CUBE suddenly becomes a lot better. 

The problem is right now, that i in the middle of a discussion between Service Provider and Customer, whereas the SP is trying to convince the customer that they don`t need the CUBE, as their service offering is based upon interop testing with CUCM 8.5(1) with early-offer, and (according to the SP) a CUBE is not required. 

Besides all the other benefits of using a CUBE, the case is hanging on the support for early-offer of endpoints right now. 

So i need this information to provide a more clear picture, regarding the "other" consequences of not using a CUBE to interface with the Service Provider. 

I have got 3 other projects lined up, where this same SP is their preffered partner for PSTN access, and i want to prevent having these same discussions again and again. 

Maybe i have clarified, the situation a bit more, and maybe you can use this internally, as seeing the Cisco documentation (New and Changed for Cisco Unified Communications Manager 8.5(1) ) -> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_5_1/delta/delta.html#wp1849900 is referencing SCCP version 20, but it is impossible to verify if the devices are actually supported. 

Hope you can help me, you can unicast me if desired or required. 

Erik Goppel 

Technical Consultant Unified Communications 

Dimension Data Netherlands. 

On Tue, Feb 21, 2012 at 9:02 PM, Wes Sisk < wsisk at cisco.com > wrote: 

There is significant disagreement on whether this information should be publicly available. To that end it generally is not documented in any customer facing material. 

/wes 

On Feb 21, 2012, at 2:00 PM, Erik Goppel wrote: 

Hi, 

I`ve been searching a lot, but i quess i need some help. 
I would like to know, how i can verify if an endpoint supports SCCP v20. 
Additionally, how can i verify which firmware version introduces SCCP v20 support. 

I am not looking for a check on a system, but i would like to know which documents on CCO can show which endpoint supports sccp v20 and in which firmware version this should be. 
I think it is starting with release 9.x of the firmware, but not completely sure. 

Please advise 

( maybe Wes knows the links :-) ) 

_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 

itevomcid 
_______________________________________________ 
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/20120221/1e731a18/attachment.html>