Anyone have a configuration for E1 in China?

Tommer Catlin · ‎02-06-2009

i'm having issues getting my E1 to work in China and Taiwan. Calls come in fine, but I cant make an outbound call. The ISDN debugs show it hitting the router and the it looks to me the carrier is rejecting it, but I have tried every different combo to make it work, no luck.

I figure if someone had another 2800 or 3800 MGCP or H.323 E1 configuration for China, it would help.

Thanks!

paolo bevilacqua · ‎02-06-2009

Show the traces.

Tommer Catlin · ‎02-06-2009

Jan 29 17:58:51.715: ISDN Se0/0/0:15 Q931: SETUP pd = 8 callref = 0x0005

Sending Complete

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Display i = '8892020'

Calling Party Number i = 0x0081, '8892020'

Plan:Unknown, Type:Unknown

Called Party Number i = 0x80, '00XXXXXXXXXX'

Plan:Unknown, Type:Unknown Jan 29 17:58:51.731: ISDN Se0/0/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=5 Jan 29 17:58:51.819: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=8 nr

=5

Jan 29 17:58:51.819: ISDN Se0/0/0:15 Q931: STATUS pd = 8 callref = 0x8005

Cause i = 0x82E3 - Information element not implemented

Call State i = 0x01

Jan 29 17:58:51.819: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=9 Jan 29 17:58:51.827: ISDN Se0/0/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=9 nr

=5

Jan 29 17:58:51.827: ISDN Se0/0/0:15 Q931: RELEASE_COMP pd = 8 callref = 0x8005

Cause i = 0x82E4 - Invalid information element contents Jan 29 17:58:51.827: ISDN Se0/0/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=10

paolo bevilacqua · ‎02-06-2009

prob 1: Bearer Capability i = 0x8090A2

that is ulaw and should be A-law

prob 2: Display i = '8892020'

switch may not like that.

Once you fix the above (details different if mgcp or h.323) you should be fine. Remember to check clocking since you're there.