[cisco-voip] sccp registration if IOS router left at sccp keyword version 4.1
Wes Sisk
wsisk at cisco.com
Thu Jun 10 10:14:30 EDT 2010
bingo. some things, such as enums for codecs, new messages, and message
order change with sccp version. /wes
On Wednesday, June 09, 2010 10:35:34 PM, Pavan K <pav.ccie at gmail.com> wrote:
> If i am not mistaken,
>
> the (ccm) version keyword in IOS is used by the router to determine
> the Skinny version used to register with CCM.
> As such a CCM v7.1 can very well understand its own skinny version and
> all previous skinny versions.
>
> That being said, an incompatible bug fix / enhancement is what causes
> a new skinny version to being added.
> so its generally recommended to be on the latest SK version.
>
>
> On Wed, Jun 9, 2010 at 1:48 PM, Ryan Ratliff <rratliff at cisco.com
> <mailto:rratliff at cisco.com>> wrote:
>
> It wouldn't.
>
> Basically with the sccp version mismatching you can expect one of
> three things to happen.
> 1. No dspfarm media resources will register.
> 2. They will register, but calls will fail.
> 3. They will register, some calls will work, others will fail in
> strange and unpredictable ways.
>
> This one is guaranteed to happen every time.
> 4. TAC will yell at you to upgrade your IOS.
>
> -Ryan
>
> On Jun 9, 2010, at 2:42 PM, Jason Aarons (US) wrote:
>
>> But this is for conferencing and transcoding, how would that
>> impact the 7965 registration process?
>>
>> *From:* Lelio Fulgenzi [mailto:lelio at uoguelph.ca
>> <mailto:lelio at uoguelph.ca>]
>> *Sent:* Wednesday, June 09, 2010 2:35 PM
>> *To:* Jason Aarons (US)
>> *Cc:* cisco-voip
>> *Subject:* Re: [cisco-voip] sccp registration if IOS router left
>> at sccp keyword version 4.1
>>
>> i couldn't get a 7965 registered without the v7.1 keyword.
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Cooking with unix is easy. You just sed it and forget it.
>> - LFJ (with apologies to Mr. Popeil)
>>
>>
>> ----- Original Message -----
>> From: "Jason Aarons (US)" <jason.aarons at us.didata.com
>> <mailto:jason.aarons at us.didata.com>>
>> To: "cisco-voip" <cisco-voip at puck.nether.net
>> <mailto:cisco-voip at puck.nether.net>>
>> Sent: Wednesday, June 9, 2010 2:25:44 PM GMT -05:00 US/Canada Eastern
>> Subject: [cisco-voip] sccp registration if IOS router left at
>> sccp keyword version 4.1
>>
>>
>> What happens if a router is left running with keyword version 4.1
>> but you upgrade Callmanager to 7.1(3b)SU2 ? I can’t seem to tell
>> a problem, it looks like conf and transcoder stay registered, but
>> surely there must be a reason the keyword got updated, etc.
>>
>> Older verion IOS 2811
>> sccp
>> sccp local fastethernet0/0
>> sccp ccm 10.10.55.133 priority 1 version 4.1
>> sccp ccm 10.10.55.132 priority 2 version 4.1
>>
>>
>> Once you upgrade to 12.4.15 or higher you get keyword 7.0+
>> sccp
>> sccp local fastethernet0/0
>> sccp ccm 10.10.55.133 priority 1 version 7.0+
>> sccp ccm 10.10.55.132 priority 2 version 7.0+
>>
>>
>>
>> RouterTestIOS15-01(config)#sccp ccm 10.10.55.133 priority 1 version ?
>> 3.0 Select CCM 3.0 version or above
>> 3.1 Select CCM 3.1 version or above
>> 3.2 Select CCM 3.2 version or above
>> 3.3 Select CCM 3.3 version or above
>> 4.0 Select CCM 4.0 version or above
>> 4.1 Select CCM 4.1 version or above
>> 5.0.1 Select CCM 5.0.1 version or above
>> 6.0 Select CCM 6.0 version or above
>> 7.0+ Select CCM 7.0 version or above
>>
>>
>> ------------------------------------------------------------------------
>> *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.*
>>
>> _______________________________________________ cisco-voip
>> mailing list cisco-voip at puck.nether.net
>> <mailto:cisco-voip at puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
>> ------------------------------------------------------------------------
>>
>> *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.*
>> _______________________________________________
>>
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> --
> - Pavan
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20100610/99fc9bb7/attachment.html>
More information about the cisco-voip
mailing list