CME 7 and Older IP Phones

Answered Question
Apr 27th, 2010

I am installing CME 7 and all the phones are 7902, 7912, 7940 and 7960's. I am having trouble finding the phone loads for these to put onto the 3825. Am I missing somehing? Can someone point me in the right direction?

Thanks so much.

Rick

I have this problem too.
0 votes
Correct Answer by Rob Huffman about 3 years 12 months ago

Hi Rick,

First off, you are most welcome my friend!

We have never used a VG224 with CME but here is what I found

An alternative to using the auto assign command is to manually assign ephone-dns to ephones (analog phones on FXS ports). This method is more complicated, but you might need to use it if you want to assign a specific extension number (ephone-dn) to a particular ephone. The reason that manual assignment is more complicated is because a unique device ID is required for each registering ephone and analog phones do not have unique MAC addresses like IP phones do. To create unique device IDs for analog phones, the auto assign process uses a particular algorithm. When you make manual ephone assignments, you have to use the same algorithm for each phone that receives a manual assignment.

The algorithm uses the single 12-digit SCCP local interface MAC address on the Cisco IOS gateway as the base to create unique 12-digit device IDs for all the FXS ports on the Cisco IOS gateway. The rightmost 9 digits of the SCCP local interface MAC address are shifted left three places and are used as the leftmost 9 digits for all 24 individual device IDs. The remaining 3 digits are the hexadecimal translation of the binary representation of the port's slot number (3 digits), subunit number (2 digits), and port number (7 digits). The following example shows the use of the algorithm to create a unique device ID for one port:

a. The MAC address for the Cisco VG224 SCCP local interface is 000C.8638.5EA6.

b. The FXS port has a slot number of 2 (010), a subunit number of 0 (00), and a port number of 1 (0000001). The binary digits are strung together to become 0100 0000 0001, which is then translated to 401 in hexadecimal to create the final device ID for the port and ephone.

c. The resulting unique device ID for this port is C863.85EA.6401.

When manually setting up an ephone configuration for an analog port, assign it just one button because the port represents a single-line device. The button command can use the ":" (colon, for normal), "o" (overlay) and "c" (call-waiting overlay) modes.

http://www.ciscosystems.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmebasic.html#wp1182120

Cheers!

Rob


Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

Correct Answer by Rob Huffman about 3 years 12 months ago

Hi Rick,

No worries

Here is an example for the Firmware files for the 7940/7960

Voice and Unified Communications > IP Phones > Cisco Unified IP Phone 7900 Series > Cisco Unified IP Phone 7940G > Skinny Client Control Protocol (SCCP) Software > 8.1(2) > cmterm-7940-7960-sccp.8-1-2.zip

Cheers!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (2 ratings)
Correct Answer
Rob Huffman Tue, 04/27/2010 - 07:47

Hi Rick,

No worries

Here is an example for the Firmware files for the 7940/7960

Voice and Unified Communications > IP Phones > Cisco Unified IP Phone 7900 Series > Cisco Unified IP Phone 7940G > Skinny Client Control Protocol (SCCP) Software > 8.1(2) > cmterm-7940-7960-sccp.8-1-2.zip

Cheers!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

wrickk_2 Tue, 04/27/2010 - 08:01

Awesome, thank you, Rob.

One more question you may have the answer to, there is also a VG224 which I have never setup with CME, only CUCM. Can I set that up using SCCP? If so, what MAC's do I use for the related ephones on the gateway?

Thanks again!

Correct Answer
Rob Huffman Tue, 04/27/2010 - 08:28

Hi Rick,

First off, you are most welcome my friend!

We have never used a VG224 with CME but here is what I found

An alternative to using the auto assign command is to manually assign ephone-dns to ephones (analog phones on FXS ports). This method is more complicated, but you might need to use it if you want to assign a specific extension number (ephone-dn) to a particular ephone. The reason that manual assignment is more complicated is because a unique device ID is required for each registering ephone and analog phones do not have unique MAC addresses like IP phones do. To create unique device IDs for analog phones, the auto assign process uses a particular algorithm. When you make manual ephone assignments, you have to use the same algorithm for each phone that receives a manual assignment.

The algorithm uses the single 12-digit SCCP local interface MAC address on the Cisco IOS gateway as the base to create unique 12-digit device IDs for all the FXS ports on the Cisco IOS gateway. The rightmost 9 digits of the SCCP local interface MAC address are shifted left three places and are used as the leftmost 9 digits for all 24 individual device IDs. The remaining 3 digits are the hexadecimal translation of the binary representation of the port's slot number (3 digits), subunit number (2 digits), and port number (7 digits). The following example shows the use of the algorithm to create a unique device ID for one port:

a. The MAC address for the Cisco VG224 SCCP local interface is 000C.8638.5EA6.

b. The FXS port has a slot number of 2 (010), a subunit number of 0 (00), and a port number of 1 (0000001). The binary digits are strung together to become 0100 0000 0001, which is then translated to 401 in hexadecimal to create the final device ID for the port and ephone.

c. The resulting unique device ID for this port is C863.85EA.6401.

When manually setting up an ephone configuration for an analog port, assign it just one button because the port represents a single-line device. The button command can use the ":" (colon, for normal), "o" (overlay) and "c" (call-waiting overlay) modes.

http://www.ciscosystems.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmebasic.html#wp1182120

Cheers!

Rob


Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

wrickk_2 Tue, 04/27/2010 - 08:43

Wow, that sounds painful.

I unfortunately have to assign specific dn's to all those analog phones.

Thanks my friend, take care.

wrickk_2 Sat, 05/01/2010 - 09:00

Hey Rob,

I got this working using the SCCP auto register, all the ephones were created automatically in CME then it was just a matter of creating DN's and assiging them to the ephones based on the hex value of the port which acts as the last 3 digits of the MAC as stated in above document you previously linked. In my case in went like this..

2/0 - 400

2/1 - 401

2/2 - 402

2/3 - 403

2/4 - 404

2/5 - 405

2/6 - 406

2/7 - 407

2/8 - 408

2/9 - 409

2/10 - 40A

2/11 - 40B

2/12 - 40C

2/13 - 40D

2/14 - 40E

2/15 - 40F

2/16 - 410

2/17 - 411

2/18 - 412

2/19 - 413

2/20 - 414

2/21 - 415

2/22 - 416

2/23 - 417

I am still having one problem, if I dial in calls work fine... dialing out there is no dialtone just a fast busy as soon as the receiver is picked up. Any ideas?

wrickk_2 Sat, 05/01/2010 - 11:21

Nevermind, I fixed it. The dial-peers for MGCP (VG224 was previously setup as MGCP/SRST) were still in the VG224, deleted those and everything is working fine.

Actions

Login or Register to take actions

This Discussion

Posted April 27, 2010 at 7:31 AM
Stats:
Replies:6 Avg. Rating:5
Views:565 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 21,031
2 15,047
3 10,323
4 8,014
5 4,856
Rank Username Points
124
105
98
57
56