Problem with CUCM MGCP E1

[kamil_folga]

Hi,

I have connection beetween two CUCM 8.6 with E1 (MGCP). E1s was registered in CUCMs. Route pattern works on each of CUCM:

CUCM 1 (number 9XX, pattern 5XX)  to  CUCM 2(number 5xx, pattern 9XX)

Route pattern send voice from CUCM to E1, but on CUCM2 E1 nothing call.

Log:

*Aug 20 07:47:37.495: ISDN Se1/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=0
*Aug 20 07:38:39.899: ISDN Se1/0/0:15 Q921: User TX -> RRp sapi=0 tei=0 nr=0
*Aug 20 07:38:39.899: ISDN Se1/0/0:15 Q921: User TX -> RRf sapi=0 tei=0 nr=0
*Aug 20 07:38:39.903: ISDN Se1/0/0:15 Q921: User RX <- RRf sapi=0 tei=0 nr=0
*Aug 20 07:38:41.391: ISDN Se1/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=0 nr=0
*Aug 20 07:38:41.391: ISDN Se1/0/0:15 Q931: SETUP pd = 8  callref = 0x0001
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA9839F
                Exclusive, Channel 31
        Calling Party Number i = 0x0081, '991'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0x80, '502'
                Plan:Unknown, Type:Unknown
*Aug 20 07:38:41.399: ISDN Se1/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=1
*Aug 20 07:38:45.875: ISDN Se1/0/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=1 nr=0

What`s wrong?

Sincerely,

Kamil

[Jaime Valencia]

There's no way to tell you if you only send the SETUP message...

Check all the related config, MGCP config, RG/RL/RP, inbound CSS, significant digits, etc.

[kamil_folga]

I think is e1 problem, because on e1 on other side debugging q921/q931 nothing shows up.

I dont have CSS, significant digits.

[Jaime Valencia]

What does the sh isdn status shows on both sides??

[kamil_folga]

Layer 1 Status:

ACTIVE

Layer 2 Status:

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

[Mohammed al Baqari]

Hi,

Are both CUCMs in single cluster or separate clusters?  How are you forcing the calls through cluster 2?

Also check DNA report to make sure that call is going out of cluster 2. If this is confirmed, you need to share debug mgcp packet and debug isdn q931 to see what is happening during the call. Also, share the calling and called numbers.