do you have your *network-clock-participate* and
*network-clock-select*commands correctly defined on the router for
clocking?
On 2/4/08, Juan Lopez Hernandez -X (jlopezhe - IBM - INS at Cisco) <
[EMAIL PROTECTED]> wrote:
>
> Hi Scott,
>
> thanks for the reply, but I already tried what you suggested: no mgcp/mgcp
> removed the original 'TEI ASSIGNED' indication, I've also reset the GW on
> the CCM, but with no results (the 'test' dial-peer 999 was removed too).
> That was why I was thinking about a missing command somewhere. I suppose -
> as it's all ISDN related signaling - having a connection NM-HDV2 to NM-HDV
> shouldn't cause any problem? Either way, I've put back the NM-HDV instead of
> the NM-HDV2, and everything was working again... gonna keep it like that
> now, and if I find some extra time, I'll have another look at it - but Thank
> You for the help!
>
> Kind regards,
> Juan
>
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Scott Monasmith
> *Sent:* Monday, February 04, 2008 9:49 PM
> *To:* Juan Lopez Hernandez -X (jlopezhe - IBM - INS at Cisco)
> *Cc:* ccie_voice@onlinestudylist.com
> *Subject:* Re: [OSL | CCIE_Voice] MGCP PRI L2 issue
>
>
> Juan,
>
> Remove dial-peer v 999 pots - You don't need this for the PRI.
> Then do a 'no mgcp' then 'mgcp' - Maybe reset the gateway on CCM as well
> and you should be good to go.
>
> Cheers,
> Scott
>
>
> On Feb 2, 2008 3:30 PM, Juan Lopez Hernandez -X (jlopezhe - IBM - INS at
> Cisco) <[EMAIL PROTECTED]> wrote:
>
> > Hi all,
> >
> > today, I swapped some HW in my lab, replacing the NM-HDV by
> > NM-HDV2-1T1/E1. I had a working MGCP GW, connected via PRI to the PSTN. When
> > using the NM-HDV2, I expercience a L2 issue (see debug below), causing all
> > calls over that PRI to fail. I doubt that the HW is broken in this case, and
> > it's a matter of a missing command... Does anybody have a clue or
> > experienced the same - please let me know. I attached the config used on the
> > GW - it's functionally not different from the working one when using the
> > NM-HDV.
> >
> > ps: I have a PVDM2 sitting on the NM-HDV2, from which a part will be
> > used as dspfarm ('voice-card 1')
> >
> > Kind regards,
> > Juan
> >
> >
> >
> >
> > isdn switch-type primary-ni
> > voice-card 1
> > dspfarm
> > dsp services dspfarm
> >
> > controller T1 1/1
> > framing esf
> > linecode b8zs
> > cablelength short 133
> > pri-group timeslots 1-3,24 service mgcp
> >
> > interface Serial1/1:23
> > no ip address
> > isdn switch-type primary-ni
> > isdn incoming-voice voice
> > isdn bind-l3 ccm-manager
> > no cdp enable
> >
> > voice-port 1/1:23
> >
> > dial-peer voice 999 pots
> > application mgcpapp
> > incoming called-number .
> > port 1/1:23
> >
> > BR1-RTR#sh isdn status
> > Global ISDN Switchtype = primary-ni
> >
> > %Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may
> > not apply
> >
> > ISDN Serial1/1:23 interface
> > dsl 0, interface ISDN Switchtype = primary-ni
> > L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003
> > Layer 1 Status:
> > ACTIVE
> > Layer 2 Status:
> > TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
> > Layer 3 Status:
> > 0 Active Layer 3 Call(s)
> >
> > BR1-RTR#debug isdn q921
> > debug isdn q921 is ON.
> > BR1-RTR#term mon
> > BR1-RTR#
> > Feb 2 21:21:20.940: ISDN Se1/1:23 Q921: S7_T203_EXPIRY: Lost
> > communication with remote.
> > Feb 2 21:21:20.940: ISDN Se1/1:23 Q921: User TX -> RRp sapi=0 tei=0
> > nr=0
> > Feb 2 21:21:20.944: ISDN Se1/1:23 Q921: User RX <- RRp sapi=0 tei=0
> > nr=0
> > Feb 2 21:21:20.944: ISDN Se1/1:23 Q921: User TX -> RRf sapi=0 tei=0
> > nr=0
> > Feb 2 21:21:20.944: ISDN Se1/1:23 Q921: User RX <- RRf sapi=0 tei=0
> > nr=0
> >
> >
> >
>
>
>
> --
> "There are only 10 types of people in the world: Those who understand
> binary, and those who don't"
>
--
Ovais Iqbal
416-294-7869
