cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
500
Views
0
Helpful
9
Replies

VG224 registration ISSUE with CUCM 7

wilsonsant
Level 6
Level 6

Hi Guys,

 

I need to invert the registration VG224 of CUCM Publisher to CUCM Subscriber. The previous configuration was:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

but, didn´t worked. Are another configuration to change? In the CUCM I need to do changes?

 

Thanks,

 

Wilson

2 Accepted Solutions

Accepted Solutions

Gordon Ross
Level 9
Level 9

You need to change the CUCM Group/Device Pool for the VG224 ports.

 

GTG

Please rate all helpful posts.

View solution in original post

Original:

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0  <--- This is ID #1
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1  <--- This says to use ID #1 first
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0  <--- This is ID #2
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1  <--- This says to use ID #2 first
 associate ccm 1 priority 2

 

As you can see in the original config, ID #1 is used first which is 10.20.4.230.

In the changed config, ID #2 is used first which is also 10.20.4.230

End result is that 10.20.4.230 is used in either case.

 

 

 

 

 

 

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

- See more at: https://supportforums.cisco.com/discussion/12512316/vg224-registration-issue-cucm-7#sthash.SdUNrnfj.dpuf

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

- See more at: https://supportforums.cisco.com/discussion/12512316/vg224-registration-issue-cucm-7#sthash.SdUNrnfj.dpuf

View solution in original post

9 Replies 9

Gordon Ross
Level 9
Level 9

You need to change the CUCM Group/Device Pool for the VG224 ports.

 

GTG

Please rate all helpful posts.

Hi Gordon,


Thanks a lot for Your contact. This configuration that You mentioning is of CUCM side?

 

Thanks,


Wilson

Yes, in CCMAdmin.

 

GTG

Please rate all helpful posts.

Also, the changes to the SCCP group did not change anything.

You started with CCM ID 1 (10.20.4.230) as the first CCM to try to register with.

Then you changed it to CCM ID 2 is the first CCM to use but at the same time you changed CCM ID 2 = 10.20.4.230. The end result is 10.20.4.230 is used first for both situations. You can change the IP address assigned to an ID or the priority of the ID but if you change both you end up back where you started.

 

 

 

 

 

Hi kkoeper12,

 

I am sorry, but, I didn´t understand, stay confuse your explanation.

 

Thanks,

 

Wilson

Original:

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0  <--- This is ID #1
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1  <--- This says to use ID #1 first
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0  <--- This is ID #2
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1  <--- This says to use ID #2 first
 associate ccm 1 priority 2

 

As you can see in the original config, ID #1 is used first which is 10.20.4.230.

In the changed config, ID #2 is used first which is also 10.20.4.230

End result is that 10.20.4.230 is used in either case.

 

 

 

 

 

 

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

- See more at: https://supportforums.cisco.com/discussion/12512316/vg224-registration-issue-cucm-7#sthash.SdUNrnfj.dpuf

sccp local FastEthernet0/0
sccp ccm 10.20.4.230 identifier 1 version 7.0
sccp ccm 10.20.4.231 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 1 priority 1
 associate ccm 2 priority 2

 

Now I putted:

 

sccp local FastEthernet0/0
sccp ccm 10.20.4.231 identifier 1 version 7.0
sccp ccm 10.20.4.230 identifier 2 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

- See more at: https://supportforums.cisco.com/discussion/12512316/vg224-registration-issue-cucm-7#sthash.SdUNrnfj.dpuf

Hi Gordon and kkoeper12,

 

I changed the configuration (reverse put ccm subscriber priority 1 and ccm publisher priority 2) and didn´t work. I erase the configuration and include only cucm subscriber, but, didn´t worked too. The analog phone not register in CUCM.

 

Thanks,


Wilson

 

 

Hi Gordon and Kkoeper12,

 

Today I did again the configuration (erase the parameters about sccp and create) and worked.

 

Thanks a lot for your help,.

 

Wilson

Hi Gordon and kkoeper12,

Hi kkoeper12,

 

In the really the configuration actuall is:

 

sccp local FastEthernet0/0
sccp ccm 10.224.4.251 identifier 2 version 7.0
sccp ccm 10.224.4.252 identifier 1 version 7.0
sccp
!
sccp ccm group 1
 bind interface FastEthernet0/0
 associate ccm 2 priority 1
 associate ccm 1 priority 2

 

Thanks,


Wilson