CME QCT toll does not recognize T1/E1 card

[sean.reardon]

When I use the "Auto detec hardware" option in the 3.1 QCT tool, it finds the Unity Express & 4 port FXO but it does not detect the T1/E1 card. The router is a 2821 CME 4.0 and CUE 3.0. Is this normal or should it detect it?

[paolo bevilacqua]

Hello, a friendly advice, for professional results and more importantly to understand what you're doing, forget qct and gui tools and only use cli to configure CME. In particular the T1/E1 card only requires 4-5 commands that I can summarize here for you if you tell us where you are and which telco service you got.

[sean.reardon]

In the US. It's an AT&T T-1. ISDN PRI 23 channels. Here is what shows up in the CLI output form the QCT tool

card type t1 0

card type t1 0 0

!

isdn switch-type primary-4ess

!

controller t1 0/0/0

default mode

line b8zs

framing esf

clock source line

pri-group timeslots 1-23

no shutdown

Thanks

Sean

[paolo bevilacqua]

A "corrected" config would be:

card type t1 0

network-clock-participate wic 0

network-clock-select 1 t1 0/0/0

isdn switch-type primary-5ess

controller t1 0/0/0

pri-group timeslots 1-23

no shutdown

dial-peer voice 100 pots

desc ld calls

destination-pattern 91[2-9][0-8][0-9][2-9]......

port 0/0/0:23

forward-digits 11

dial-peer voice 101 pots

desc lata calls

destination-pattern 9[2-9]......

forward-digits 7

port 0/0/0:23

dial-peer voice 102 pots

desc international

destination-pattern 9011......T

port 0/0/0:23

prefix 011

dial-peer voice 103 pots

desc *11

destination-pattern 9[2469]11

port 0/0/0:23

forward-digits 3

dial-peer voice 911 pots

destination-pattern 911

port 0/0/0:23

forward-digits 3

The config for DP is a bit verbose but will allow you to:

1- prevent misdialed calls by strict nanp checking

2- count how many calls are done and where with "show dial-peer voice"

3- enforce limitations based on calling phone for what is callable and what is not.

You will find that CME is a very powerful PBX but it takes some time to master it. it's time well spent anyway.

Hope this helps, please rate post if it does!

[sean.reardon]

Paulo,

Great advice. Works like a champ Calls now ring into the phones. One more question: Calls come into the system fine but when I dail 91(xxx)xxx-xxxx I am getting a busy signal. Does the config you provided handle outcalling or is that something I need to fiddle with in the user parameters?

[paolo bevilacqua]

Well the idea was a to give you a config for outcalling ...

can you take "debug isdn q931" with "term mon" when you make an outgoing call ?

[sean.reardon]

Paulo/ anyone,

Here is the output from the ISDN Debug Q931. I tried to dial a 10 digit #/ As you see the error is: Cause i = 0x83E020 - Mandatory information element missing. Any suggestions?

debug isdn q931 is ON.

Singapore#

Mar 28 12:31:36.999: ISDN Se0/0/0:23 Q931: Applying typeplan for sw

0x2 0x1, Calling num 80001

Mar 28 12:31:37.003: ISDN Se0/0/0:23 Q931: Applying typeplan for sw

0x2 0x1, Called num 19788771761

Mar 28 12:31:37.003: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 call

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x2180, '80001'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '19788771761'

Plan:ISDN, Type:National

Mar 28 12:31:37.047: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd =

0x8087

Cause i = 0x83E020 - Mandatory information element missing

[paolo bevilacqua]

Hi, somewhere in the config, do have a command that sets "ISDN national" ? If so, please remove it. Also please add:

int serial 0/0/0:23

isdn sending-complete