Fast Busies on Outbound

[Midnite1971]

Hi Everyone,

We get fast busies randomly on outbound calls...no pattern for it and there are trunks available. Any ideas?

CS1000 4.5

Thanks
Tim

 

[johnpoole]

best bet would be the set up either entc on a set and duplicate the problem or enl msgo on your d..

john poole
bellsouth business
columbia,sc

 

[GHTROUT]

The fast busy can also be because of telephone company network capacity. When you hear the busy, if you can "put the busy on hold" then it's the for sure the network.

You can't put a system (i.e. PBX generated) busy signal on hold.

If you use PRI, this test isn't a valid one though.

GHTROUT.com | FAQs | Recent Replies

 

[Midnite1971]

We do use PRIs and the most I've ever seen them is about half busy....but the complaints from users keep on coming in.....at least 5 to 10 a day. It's really starting to get annoying....never seen this issue before.

 

[tnphoneman]

CS1000 What? Which one is it? E M? cabinet or columns. processor type?

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[StanleySteamer]

Midnite1971 - Take a look at the MAX in the RDB for your outgoing route(s). That is what really tells you how many trunks you have for outgoing calls. But you really need to look at the MIN/MAX for all routes. You may have an incoming route with a high MIN that is preventing outgoing calls, even though it appears you have channels available.

 

[StanleySteamer]

Meant to say that you could also look at the traffic reports.

 

[Midnite1971]

Where would I find the min/max for a route?

 

[PERRYPJ]

I have the same problem every so often, I have 3 PRI's which is over trunked for me. When I get the busy I just hit Redial and the call goes through. I suspect Telco is experiencing ATB's in there trunks to other Central Offices

OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[StanleySteamer]

Where would I find the min/max for a route?

In the RDB of the service routes.

 

[phonz1]

MIN and Max only show in ISA routes

 

[Triton101]

If your PRIs dropped recently (before the problem) or you had an INI before this started, the what you might have is a missmatch in channel status bettween the PBX and the CO (DMS or ESS). What you might want to do is drop all the PRI loops (off hours) and bring them up, that ususaly clears channel missmatches....

good luck

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[Midnite1971]

OK....today was another one of those that for about a 10 minute period, all outgoing calls got fast busies. This is starting to piss me off. I just started at this company so I'm following somebody else's work....I can't find anything wrong. I'll contact the CLEC tomorrow and compare notes on DCHs and crap.

Just in case anyone has an idea...here's the DCHs, RDB, and a TRK.
Thanks

ADAN DCH 1
CTYP MSDL
DNUM 14
PORT 3
DES PAETEC
USR PRI
DCHL 25
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP NDS
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

ADAN DCH 5
CTYP MSDL
DNUM 14
PORT 1
DES PAETEC
USR PRI
DCHL 13
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

TYPE RDB
CUST 00
ROUT 23
DES PAETEC
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS YES
NDGT 4
DDLY NO
DCDR YES
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 7123
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 1 *
NDNO 1
DNAM YES
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
IENB 5
VSS 0
VGD 6
DRNG YES
NDRI 00
CDR YES
INC YES
LAST YES
TTA YES
ABAN YES
CDRB NO
QREC YES
OAL YES
AIA YES
OAN YES
OPD NO
CDRX NO
NATL YES
VRAT NO
MUS YES
MRT 10
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TDET NO
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO


DES PAETEC
TN 013 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 23 24
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE NO DATE

 

[PERRYPJ]

I have a Paetec ISDN-PRI will post tomorrow

OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[StanleySteamer]

Good point phonz1. Sorry Midnite1971 - I was thinking ISA trunks.
You may get some clue by TRACing a phone like
TRAC lll s cc uu DEV

ALso maybe turn on DCH messages. Be prepared to turn it off if it's crazy busy.

 

[Midnite1971]

I did turn it on and we got a few fast busies....I really don't know how to read this thing though when we do get a fast busy......help anyone?
Thanks!

There was a fast busy at 3:49.
Called Number: 703-784-9200

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A17 CH 13 14 TOD 15:48:28 CK 7F1A8B8C
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18005309973 NUM PLAN: E164 TON: NATL
CALLED #:7035509740 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A18 CH 13 13 TOD 15:48:28 CK 7F1A8D9D
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18005496367 NUM PLAN: E164 TON: NATL
CALLED #:19086078590 NUM PLAN: E164 TON: NATL

DCH 1 UIPE_OMSG CC_SETUP_RESP REF 00009601 CH 25 2 TOD 15:48:30 CK 7F1A9406
PROGRESS: TERMINATING END IS NOT ISDN
CONNECT #:5926 NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 5 UIPE_OMSG CC_DISC_REQ REF 000009E3 CH 13 22 TOD 15:48:30 CK 7F1A953C
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 000009E3 CH 13 22 TOD 15:48:30 CK 7F1A95A
7
set
DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A19 CH 13 22 TOD 15:48:31 CK 7F1AA435
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:7039255644 NUM PLAN: E164 TON: NATL
CALLED #:16173734051 NUM PLAN: E164 TON: NATL
ms
DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1A CH 13 11 TOD 15:48:31 CK 7F1AABD5
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:7039257648 NUM PLAN: E164 TON: NATL
CALLED #:7034352555 NUM PLAN: E164 TON: NATL
go 1 mon
.
DCH 5 UIPE_OMSG CC_DISC_REQ REF 000009DA CH 13 20 TOD 15:48:37 CK 7F1AD76D
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 000009DA CH 13 20 TOD 15:48:37 CK 7F1AD7C
2

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A10 CH 13 17 TOD 15:48:37 CK 7F1AE0FD
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A10 CH 13 17 TOD 15:48:37 CK 7F1AE16
E

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1B CH 13 20 TOD 15:48:40 CK 7F1AE46D
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18002919326 NUM PLAN: E164 TON: NATL
CALLED #:19493957329 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1C CH 13 17 TOD 15:48:50 CK 7F1B3AA5
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8005752240 NUM PLAN: E164 TON: NATL
CALLED #:15183582222 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1D CH 13 10 TOD 15:48:53 CK 7F1B548D
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645495 NUM PLAN: E164 TON: NATL
CALLED #:7033906000 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A1B CH 13 20 TOD 15:48:53 CK 7F1B598E
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A1B CH 13 20 TOD 15:48:53 CK 7F1B59E
9

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1E CH 13 20 TOD 15:48:56 CK 7F1B6AA5
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849020 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A1E CH 13 20 TOD 15:48:57 CK 7F1B7605
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A1E CH 13 20 TOD 15:48:57 CK 7F1B765
F

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A1F CH 13 20 TOD 15:49:03 CK 7F1B9DBF
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18008438733 NUM PLAN: E164 TON: NATL
CALLED #:19134888626 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A20 CH 13 9 TOD 15:49:07 CK 7F1BBC07
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849200 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A20 CH 13 9 TOD 15:49:07 CK 7F1BC575

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A21 CH 13 9 TOD 15:49:16 CK 7F1C0147
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849200 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A21 CH 13 9 TOD 15:49:16 CK 7F1C0A32

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A22 CH 13 9 TOD 15:49:18 CK 7F1C1497
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18005465318 NUM PLAN: E164 TON: NATL
CALLED #:12025026166 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A23 CH 13 8 TOD 15:49:19 CK 7F1C20E7
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849200 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A23 CH 13 8 TOD 15:49:22 CK 7F1C2A9E

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A24 CH 13 8 TOD 15:49:23 CK 7F1C3FA7
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849200 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A24 CH 13 8 TOD 15:49:25 CK 7F1C4918

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A25 CH 13 8 TOD 15:49:25 CK 7F1C5149
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18004679710 NUM PLAN: E164 TON: NATL
CALLED #:18148654038 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A11 CH 13 16 TOD 15:49:32 CK 7F1C8351
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A11 CH 13 16 TOD 15:49:32 CK 7F1C83C
0

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A26 CH 13 16 TOD 15:49:32 CK 7F1C84AA
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003324517 NUM PLAN: E164 TON: NATL
CALLED #:7034013895 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A27 CH 13 6 TOD 15:49:34 CK 7F1C9389
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18884420733 NUM PLAN: E164 TON: NATL
CALLED #:14085464598 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A28 CH 13 3 TOD 15:49:38 CK 7F1CA782
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18008438733 NUM PLAN: E164 TON: NATL
CALLED #:19497668550 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A29 CH 13 1 TOD 15:49:41 CK 7F1CC9F2
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18002919326 NUM PLAN: E164 TON: NATL
CALLED #:12122787247 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A18 CH 13 13 TOD 15:49:41 CK 7F1CCDAA
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A18 CH 13 13 TOD 15:49:41 CK 7F1CCE2
5

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A2A CH 13 13 TOD 15:49:44 CK 7F1CE16A
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18002919319 NUM PLAN: E164 TON: NATL
CALLED #:18042363159 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A1C CH 13 17 TOD 15:49:45 CK 7F1CE8C0

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A19 CH 13 22 TOD 15:49:45 CK 7F1CE9E3
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A19 CH 13 22 TOD 15:49:45 CK 7F1CEA4
0

DCH 1 UIPE_OMSG CC_DISC_REQ REF 00009301 CH 25 7 TOD 15:49:45 CK 7F1CF0DA
CAUSE: #16 - NORMAL CALL CLEARING

DCH 1 UIPE_OMSG CC_RELEASE_RESP REF 00009301 CH 25 7 TOD 15:49:45 CK 7F1CF160


DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A0F CH 13 23 TOD 15:49:48 CK 7F1D0451
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A0F CH 13 23 TOD 15:49:48 CK 7F1D04A
B

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A0D CH 13 4 TOD 15:49:51 CK 7F1D1781
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A0D CH 13 4 TOD 15:49:51 CK 7F1D17E1


DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A2B CH 13 23 TOD 15:49:51 CK 7F1D2049
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8005752240 NUM PLAN: E164 TON: NATL
CALLED #:15183582222 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A27 CH 13 6 TOD 15:50:00 CK 7F1D5A4B
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A27 CH 13 6 TOD 15:50:00 CK 7F1D5AC7


DCH 1 UIPE_OMSG CC_PROCEED_REQ REF 00009681 CH 25 3 TOD 15:50:01 CK 7F1D6320

DCH 1 UIPE_OMSG CC_ALERT_REQ REF 00009681 CH 25 3 TOD 15:50:01 CK 7F1D6321
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A28 CH 13 3 TOD 15:50:01 CK 7F1D7023
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A28 CH 13 3 TOD 15:50:01 CK 7F1D7078


DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A2C CH 13 22 TOD 15:50:13 CK 7F1DC96C
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18003645730 NUM PLAN: E164 TON: NATL
CALLED #:7037849200 NUM PLAN: E164 TON: NATL

DCH 5 UIPE_OMSG CC_RELEASE_REQ REF 00000A2C CH 13 22 TOD 15:50:16 CK 7F1DD2BC

DCH 5 UIPE_OMSG CC_SETUP_REQ REF 00000A2D CH 13 22 TOD 15:50:16 CK 7F1DD9BD
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:18005496367 NUM PLAN: E164 TON: NATL
CALLED #:15409836258 NUM PLAN: E164 TON: NATL

DCH 1 UIPE_OMSG CC_SETUP_RESP REF 00009681 CH 25 3 TOD 15:50:22 CK 7F1E057B
CONNECT #:5959 NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A17 CH 13 14 TOD 15:50:23 CK 7F1E1535
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A17 CH 13 14 TOD 15:50:23 CK 7F1E15A
6

DCH 5 UIPE_OMSG CC_DISC_REQ REF 00000A15 CH 13 19 TOD 15:50:23 CK 7F1E1804
CAUSE: #16 - NORMAL CALL CLEARING

DCH 5 UIPE_OMSG CC_RELEASE_RESP REF 00000A15 CH 13 19 TOD 15:50:23 CK 7F1E188
8

DCH 1 UIPE_OMSG CC_RELEASE_REQ REF 00009681 CH 25 3 TOD 15:50:23 CK 7F1E1BC5

 

[PERRYPJ]

I see nothing wrong with the DCH messaging normal setup and tare down, here is my PAETEC ISDN-PRI setup

ADAN DCH 44
CTYP TMDI
CARD 44
PORT 1
DES Loop44
USR PRI
DCHL 44
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP NDS
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

TYPE RDB
CUST 00
DMOD
ROUT 1
DES LDPRI
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00000
NCNA YES
NCRD NO
CHTY BCH
CPFXS YES
CPUB ON
DAPC NO
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 7801
TCPP NO
PII NO
TARG 01
CLEN 10
BILN NO
OABS
INST
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096



PAGE 002

IENB 5
VSS 0
VGD 6
DRNG NO
CDR YES
INC YES
LAST NO
QREC NO
OAL YES
AIA NO
OAN YES
OPD YES
CDRX NO
NATL YES
VRAT NO
MUS NO
EQAR NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO


DES LDPRI
TN 044 01
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 1 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID


OLD ROLMEN WORKING ON NORTELS AND AVAYA

 

[Midnite1971]

Yours does look alot like mine.....that's why I said I couldn't find anything wrong with the programming.
The dch messaging looks ok? You can clearly see that he tried the call three times while getting a fast busy on 2 of them. What in that message tells me that he got a fast bust and why?

Thanks

 

[StanleySteamer]

Looks like you turned on outgoing messages but not incoming.
So we can't see why the call was rejected by the CO.

Did you try a TRAC with the DEV parameter?

 

[Midnite1971]

So then it was rejected by the CO and not in my PBX right? I'll try and get a trac of one of these....I can turn on ENTC, but that's a pain....and I don't think it gives you the NARS BARS crap.

Thanks