Sporadic Issue

[JarLax]

Hey guys,

I am currently having a sporadic issue that is getting annoying. Users are currently experiencing dead air on an outbound. They would try to dial the number a few times and then eventually it connects. This doesn’t happen often but lately it’s been happening a few times a day. I had the Telco run tests on the PRI’s and they weren’t able to see anything. I gave them sample call with a time and they never saw the call hit their trunk. I check my call accounting system to see if the call ever made it but it didn’t catch the call either.

All users on 4621 voip phones
Duel S8720 Servers running CM 3.1

 

[JarLax]

Any help would be appreciated.

Thanks

 

[admsr]

can you post your trunk group and ds1 configuration?

i had some problems and found that my ds1's were set to 3.1k. changed them to speech and cleared everything up. this however was geared more towards international calls but you never know.

Alex.

 

[9mmgeek]

Any chance your are running out of trunks? I don't know where or if there are settings for the kind of notification the caller would get.

 

[donbott]

do "list meas blockage pn y/t/d" and see if there is a blockage issue

DonBott

 

[JarLax]

This is the Trunk setup (114 members)
Would the busy threshold cause the issue since it is set to 68?

I did the list blockage and there was none. I checked the dsp resources as well. Since the issue is sporadic, its hard to capture it.


Trunk Group setup
---------------
Group Number: 1 Group Type: isdn CDR Reports: y
Group Name: Net 2000 I/O COR: 10 TN: 1 TAC: 8001
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 68 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: descend QSIG Value-Added? n
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format: pub-unk
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n

TRUNK FEATURES
ACA Assignment? n Measured: both Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: y
Used for DCS? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y
Network Call Redirection: none Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? n
Send Codeset 6/7 LAI IE? n Ds1 Echo Cancellation? n
Apply Local Ringback? n US NI Delayed Calling Name Update? n
Network (Japan) Needs Connect Before Disconnect? n

QSIG TRUNK GROUP OPTIONS
SBS? n


DS1 Setup
--------------------
DS1 CIRCUIT PACK

Location: 01A13 Name: Net2000
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: network
TN-C7 Long Timers? n Country Protocol: 1
Interworking Message: PROGress Protocol Version: a
Interface Companding: mulaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz

T303 Timer(sec): 4


Slip Detection? n Near-end CSU Type: integrated

 

[admsr]

are they trying to dial any particular number when the experience the dead air condition? country?

everything looks good with the exception that you do in fact have your DS1 set to "DCP/Analog Bearer Capability: 3.1kHz"

Like I mentioned earlier, I changed mine to speech.

Alex.

 

[JarLax]

Seems that the Telco might have seen an issue on their end. I am waiting to hear back from them or it might mysteriously work with no issue found on their end. I will keep you updated and thanks for the response.