Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Possible CallManager 6.0 Issue

Hello All,

I have a VG 224 for my analog devices. I need to setup one of the 23 channels for EXT 2222 in Call Manager 6.0. I assigned the Extension under the gateway tab in Call Manager 6.0. I selected the VG 224 in Call Manager I then went to configure port 19. I clicked on Line and entered my EXT number there and clicked save and reset. However when I go to the analog phone and try to dial a internal EXT or any Ext I get dial-a-tone and a fast busy. I am having the guy that punched the cable down on port 19 on the 66 block to confirm he really did punch the cable down on the correct port. Am I doing something wrong?

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Possible CallManager 6.0 Issue

What protocol are you using for the VG224? MGCP or SCCP?

Do you have the dial-peer on the VG224 configured correctly for the selected protocol?

MGCP Example:

dial-peer voice 999219 pots

service mgcpapp

port 2/19

SCCP Example:

dial-peer voice 999219 pots

service stcapp

port 2/19

Also, just because I have had techs do this before, VG224 port numbering starts at 0, so you need to make sure you are connecting to the correct port.

Thanks,

Adam

Please rate if helpful

Hall of Fame Super Red

Re: Possible CallManager 6.0 Issue

Hi Charlie,

Just to add a note to the excellent info from Adam (+5 points here Adam :)

Please try to use this method to completely remove the DN in question before trying to re-build again.

**Remove DN xxxx (the one that was previously used on the IP Phone) from the phone first;

Deleting Unassigned Directory Numbers

This section describes how to delete an unassigned directory number from the route plan report. Directory numbers get configured and removed in the Directory Number Configuration window of Cisco CallManager Administration. When a directory number gets removed from a device or a phone gets deleted, the directory number still exists in the Cisco CallManager database. To delete the directory number from the database, use the Route Plan Report window.

Procedure

--------------------------------------------------------------------------------

Step 1 Choose Route Plan > Route Plan Report.

The Route Plan Report window displays. Use the three drop-down list boxes to specify a route plan report that lists all unassigned DNs.

Step 2 Three ways exist to delete directory numbers:

a. Click the directory number that you want to delete. When the Directory Number Configuration window displays, click Delete.

b. Check the check box next to the directory number that you want to delete. Click Delete Selected.

c. To delete all found unassigned directory numbers, click Delete all Found Items.

A warning message verifies that you want to delete the directory number.

Step 3 To delete the directory number, click OK. To cancel the delete request, click Cancel.

Once you have completed this process add the DN xxxx back to the phone again (**check the Calling Search Space) and try again.

Hope this helps!

Rob

4 REPLIES

Re: Possible CallManager 6.0 Issue

What protocol are you using for the VG224? MGCP or SCCP?

Do you have the dial-peer on the VG224 configured correctly for the selected protocol?

MGCP Example:

dial-peer voice 999219 pots

service mgcpapp

port 2/19

SCCP Example:

dial-peer voice 999219 pots

service stcapp

port 2/19

Also, just because I have had techs do this before, VG224 port numbering starts at 0, so you need to make sure you are connecting to the correct port.

Thanks,

Adam

Please rate if helpful

New Member

Re: Possible CallManager 6.0 Issue

I am using MGCP. Also the EXT I and using for this analog phone was taken from a IP Phone that is no longer being used on our network. That should be ok right.

New Member

Re: Possible CallManager 6.0 Issue

Thanks for solving my problem. I can belive they punch that down wrong. I will make sure that does not happened again. Thanks again. Everything is working Flawless now.

Hall of Fame Super Red

Re: Possible CallManager 6.0 Issue

Hi Charlie,

Just to add a note to the excellent info from Adam (+5 points here Adam :)

Please try to use this method to completely remove the DN in question before trying to re-build again.

**Remove DN xxxx (the one that was previously used on the IP Phone) from the phone first;

Deleting Unassigned Directory Numbers

This section describes how to delete an unassigned directory number from the route plan report. Directory numbers get configured and removed in the Directory Number Configuration window of Cisco CallManager Administration. When a directory number gets removed from a device or a phone gets deleted, the directory number still exists in the Cisco CallManager database. To delete the directory number from the database, use the Route Plan Report window.

Procedure

--------------------------------------------------------------------------------

Step 1 Choose Route Plan > Route Plan Report.

The Route Plan Report window displays. Use the three drop-down list boxes to specify a route plan report that lists all unassigned DNs.

Step 2 Three ways exist to delete directory numbers:

a. Click the directory number that you want to delete. When the Directory Number Configuration window displays, click Delete.

b. Check the check box next to the directory number that you want to delete. Click Delete Selected.

c. To delete all found unassigned directory numbers, click Delete all Found Items.

A warning message verifies that you want to delete the directory number.

Step 3 To delete the directory number, click OK. To cancel the delete request, click Cancel.

Once you have completed this process add the DN xxxx back to the phone again (**check the Calling Search Space) and try again.

Hope this helps!

Rob

139
Views
5
Helpful
4
Replies
CreatePlease login to create content