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

Need help registering an MGCP PRI to CM 8

Hi,

I had a 2801 configured for a single, 24-channel PRI against CM 4.2 working just fine.  I decided to move to a new CallManager 8.02 and had to change the mgcp configurations in the 2801 (voip dial-peer, ccm-manager, mgcp ) to point to the new CM.

Now of course I'm stuck because the PRI will simply not come up but is stuck in the TEI_ASSIGNED state.  I have tried:

1. resetting the endpoints from within CM

2. no mgcp/mgcp on the 2801

3. shutdown, no shut on the serial 0/1:23

but nothing is good.

Troubleshooting commands

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

show isdn status

Global ISDN Switchtype = primary-4ess

ISDN Serial0/1:23 interface

        dsl 0, interface ISDN Switchtype = primary-4ess

    Layer 1 Status:

        DEACTIVATED

    Layer 2 Status:

        TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED

    Layer 3 Status:

        0 Active Layer 3 Call(s)

    Active dsl 0 CCBs = 0

    The Free Channel Mask:  0x00000000

    Number of L2 Discards = 0, L2 Session ID = 4

When I enable

debug isdn q931 and reset the PRI from the CM I see

Sep  6 05:11:15.246: %LINK-3-UPDOWN: Interface 0/1:23(22), changed state to Administrative Shutdown

.Sep  6 05:11:15.246: %LINK-3-UPDOWN: Interface 0/1:23(23), changed state to Administrative Shutdown

.Sep  6 05:11:15.711: %LINK-3-UPDOWN: Interface 0/1:23(1), changed state to Administrative Shutdown

.Sep  6 05:11:15.711: %LINK-3-UPDOWN: Interface 0/1:23(2), changed state to Administrative Shutdown

.Sep  6 05:11:15.715: %LINK-3-UPDOWN: Interface 0/1:23(3), changed state to Administrative Shutdown

.Sep  6 05:11:15.715: %LINK-3-UPDOWN: Interface 0/1:23(4), changed state to Administrative Shutdown

.Sep  6 05:11:15.719: %LINK-3-UPDOWN: Interface 0/1:23(5), changed state to Administrative Shutdown

.Sep  6 05:11:15.719: %LINK-3-UPDOWN: Interface 0/1:23(6), changed state to Administrative Shutdown

.Sep  6 05:11:15.723: %LINK-3-UPDOWN: Interface 0/1:23(7), changed state to Administrative Shutdown

.Sep  6 05:11:15.723: %LINK-3-UPDOWN: Interface 0/1:23(8), changed state to Administrative Shutdown

.Sep  6 05:11:15.727: %LINK-3-UPDOWN: Interface 0/1:23(9), changed state to Administrative Shutdown

.Sep  6 05:11:15.727: %LINK-3-UPDOWN: Interface 0/1:23(10), changed state to Administrative Shutdown

.Sep  6 05:11:15.731: %LINK-3-UPDOWN: Interface 0/1:23(11), changed state to Administrative Shutdown

.Sep  6 05:11:15.731: %LINK-3-UPDOWN: Interface 0/1:23(12), changed state to Administrative Shutdown

.Sep  6 05:11:15.735: %LINK-3-UPDOWN: Interface 0/1:23(13), changed state to Administrative Shutdown

.Sep  6 05:11:15.735: %LINK-3-UPDOWN: Interface 0/1:23(14), changed state to Administrative Shutdown

.Sep  6 05:11:15.739: %LINK-3-UPDOWN: Interface 0/1:23(15), changed state to Administrative Shutdown

.Sep  6 05:11:15.739: %LINK-3-UPDOWN: Interface 0/1:23(16), changed state to Administrative Shutdown

.Sep  6 05:11:15.743: %LINK-3-UPDOWN: Interface 0/1:23(17), changed state to Administrative Shutdown

.Sep  6 05:11:15.743: %LINK-3-UPDOWN: Interface 0/1:23(18), changed state to Administrative Shutdown

.Sep  6 05:11:15.747: %LINK-3-UPDOWN: Interface 0/1:23(19), changed state to Administrative Shutdown

.Sep  6 05:11:15.747: %LINK-3-UPDOWN: Interface 0/1:23(20), changed state to Administrative Shutdown

.Sep  6 05:11:15.751: %LINK-3-UPDOWN: Interface 0/1:23(21), changed state to Administrative Shutdown

.Sep  6 05:11:15.751: %LINK-3-UPDOWN: Interface 0/1:23(22), changed state to Administrative Shutdown

.Sep  6 05:11:15.755: %LINK-3-UPDOWN: Interface 0/1:23(23), changed state to Administrative Shutdown

.Sep  6 05:11:15.899: %CONTROLLER-5-UPDOWN: Controller T1 0/1, changed state to administratively down

.Sep  6 05:11:15.911: ISDN Se0/1:23 Q931: L3_ShutDown: Shutting down ISDN Layer 3

.Sep  6 05:11:16.035: Undefined ds0-group id

.Sep  6 05:11:16.143: Undefined ds0-group id

.Sep  6 05:11:16.251: Undefined ds0-group id

.Sep  6 05:11:16.360: Undefined ds0-group id

.Sep  6 05:11:16.468: Undefined ds0-group id

.Sep  6 05:11:16.576: Undefined ds0-group id

.Sep  6 05:11:16.684: Undefined ds0-group id

.Sep  6 05:11:16.792: Undefined ds0-group id

.Sep  6 05:11:16.901: Undefined ds0-group id

.Sep  6 05:11:17.009: Undefined ds0-group id

.Sep  6 05:11:17.117: Undefined ds0-group id

.Sep  6 05:11:17.225: Undefined ds0-group id

.Sep  6 05:11:17.333: Undefined ds0-group id

.Sep  6 05:11:17.441: Undefined ds0-group id

.Sep  6 05:11:17.550: Undefined ds0-group id

.Sep  6 05:11:17.658: Undefined ds0-group id

.Sep  6 05:11:17.766: Undefined ds0-group id

.Sep  6 05:11:17.890: Undefined ds0-group id

.Sep  6 05:11:17.998: Undefined ds0-group id

.Sep  6 05:11:18.106: Undefined ds0-group id

.Sep  6 05:11:18.215: Undefined ds0-group id

.Sep  6 05:11:18.323: Undefined ds0-group id

.Sep  6 05:11:18.431: Undefined ds0-group id

.Sep  6 05:11:18.539: Undefined ds0-group id

.Sep  6 05:11:20.799: %SYS-6-CLOCKUPDATE: System clock has been updated from 22:11:20 pdt Sun Sep 5 2010 to 22:11:20 pdt Sun Sep 5 2010, configured from console by console.

.Sep  6 05:11:20.803: %SYS-6-CLOCKUPDATE: System clock has been updated from 22:11:20 pdt Sun Sep 5 2010 to 22:11:20 pdt Sun Sep 5 2010, configured from console by console.

Attaching my 2801 configuration and a screenshot of the CM config. 

Any help is tremendously appreciated!

Everyone's tags (3)
1 REPLY
New Member

Re: Need help registering an MGCP PRI to CM 8

Ugh, nevermind.  For anyone who does this in the future, please make sure you choose the right model in CM   ( I had a 2801 instead of 1760)

1445
Views
0
Helpful
1
Replies