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

Configuring ISDN settings for E1 with China Telecom

Hello:

I am working on an integration for a client in China that has an E1 PRI with China Telecom.  Getting technical information from those guys is next to impossible...a task made more difficult because I do not speak Mandarin.  Anyway, I am having issues with caller-id and with the plan/type settings.  I am hoping someone has successfully setup a cisco voice gateway with CUCM and knows what the settings should be.

The gateway is configured as an H323.  (recently migrated from MGCP to provide support for t.37 fax onramp)

The 3 problems are itemized/summarised below.:

Thanks in advance for any insights!

scd

1.       This log info below shows a call coming from my phone in the US.  The ANI should be coming through as ‘17193578598’.  I am not sure why it is showing up as '000001901202'

We need to understand from the carrier in GZ what is happening here.  Once we get this fixed we can globalize the numbers and do better TEHO call routing from the missed/received calls directories.

PMI-GZ2821#

Sep  1 19:29:35.728: ISDN Se0/0/1:15 Q931: RX <- SETUP pd = 8  callref = 0x0025

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA1838B

                Preferred, Channel 11

        Calling Party Number i = 0x0183, '000001901202'

                Plan:ISDN, Type:Unknown

        Called Party Number i = 0x81, '87101335'

                Plan:ISDN, Type:Unknown

Sep  1 19:29:35.728: ISDN Se0/0/1:15 Q931: Received SETUP  callref = 0x8025 callID = 0x1B62 switch = primary-5ess interface = User

Sep  1 19:29:35.744: ISDN Se0/0/1:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x8025

        Channel ID i = 0xA9838B

                Exclusive, Channel 11

Sep  1 19:29:36.480: ISDN Se0/0/1:15 Q931: TX -> ALERTING pd = 8  callref = 0x8025

Sep  1 19:29:48.992: ISDN Se0/0/1:15 Q931: RX <- DISCONNECT pd = 8  callref = 0x0025

        Cause i = 0x8290 - Normal call clearing

Sep  1 19:29:48.996: ISDN Se0/0/1:15 Q931: TX -> RELEASE pd = 8  callref = 0x8025

Sep  1 19:29:49.028: ISDN Se0/0/1:15 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x0025

        Cause i = 0x8290 - Normal call clearing

2.       This information shows an OUTGOING call from extension at 1319 (DID of 87101319) to cell phone with a number of '13826153004'.  This call shows up with an ANI of 83969172 when it should show up as 87101319.  Also, why would we be getting the messages below of “Information Element not implemented” and “Invalid information element contents”?  I was able to resolve this issue by forcing the calling type to International.   ???

Sep  1 04:18:46.860: ISDN Se0/0/1:15 Q931: TX -> SETUP pd = 8  callref = 0x204B

                Bearer Capability i = 0x8090A3

                                Standard = CCITT

                                Transfer Capability = Speech

                                Transfer Mode = Circuit

                                Transfer Rate = 64 kbit/s

                Channel ID i = 0xA9839D

                                Exclusive, Channel 29

                Calling Party Number i = 0x2181, '87101319'

                                Plan:ISDN, Type:National

                Called Party Number i = 0xA1, '13826153004'

                                Plan:ISDN, Type:National

                Locking Shift to Codeset 6

                Codeset 6 IE 0x28  i = 'Winnie Liang - 1319'

Sep  1 04:18:46.924: ISDN Se0/0/1:15 Q931: RX <- STATUS pd = 8  callref = 0xA04B

                Cause i = 0x82E39628 - Information element not implemented

                Call State i = 0x01

Sep  1 04:18:46.932: ISDN Se0/0/1:15 Q931: RX <- STATUS pd = 8  callref = 0xA04B

                Cause i = 0x82E46C - Invalid information element contents

                Call State i = 0x01

Sep  1 04:18:46.932: ISDN Se0/0/1:15 Q931: RX <- CALL_PROC pd = 8  callref = 0xA04B

                Channel ID i = 0xA9839D

                                Exclusive, Channel 29

3. This is what the Telco is sending to the router once you made those test calls:  Once I forced the calling type to International the 'Invalid IE element' message went away but I am not sure why.  Also not sure why the IE not implemented message remains.  I think it has to do with the calling Name.

Cause i = 0x82E39628 - Information element not implemented

Cause i = 0x82E46C - Invalid information element contents

Called number: 13826153004

Calling number: 87101319

Please check with the service provider what is plan and type so can apply the configuration in the router.

Config snippets:

interface Serial0/0/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-4ess
isdn incoming-voice voice
isdn supp-service name calling
isdn outgoing ie facility
isdn outgoing ie extended-facility
isdn outgoing ie display
no cdp enable

voice translation-rule 3
rule 1 /^8710\(....\)/ /86208710\1/ type international international
rule 2 /^8710\(....\)/ /86208710\1/ type national international
rule 3 /^8710\(....\)/ /86208710\1/ type subscriber international
rule 4 /^8710\(....\)/ /86208710\1/ type unknown international
voice translation-profile InfromPSTN
translate called 1
voice translation-profile OutToPSTN
translate calling 3

3 REPLIES
Community Member

Configuring ISDN settings for E1 with China Telecom

Hi Steve,

Could you please share you E1 PRI configuration of China location if possible?

Regards,

Mesut

Community Member

Configuring ISDN settings for E1 with China Telecom

Hi Mesut:

This was years ago...I think this is the correct controller and serial interface config.  Let me know if it helps or not.

Here ya go...

controller E1 0/0/1

framing NO-CRC4

pri-group timeslots 1-31 service mgcp

interface Serial0/0/1:15

description ISDN E1 to PSTN   

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

isdn bind-l3 ccm-manager

isdn negotiate-bchan

no cdp enable

thanks...scd

Community Member

Did you get a resolution to

Did you get a resolution to your issue?  I am having the same problem.

Thanks, Richard

3539
Views
0
Helpful
3
Replies
CreatePlease to create content