asked on

Calls disconnect after received by user

I'm having an issue with my PBX. We are currently running CME 7.1.5.

We receive calls from an 888 number that hits a hunt group. Incoming calls will disconnect after any time up to about a minute. Also, we are receiving a crackling sound on calls randomly.

I've experienced the crackling on phone with than the hunt group phones so I'm not totally sure if it's isolated to just those phone. I've also tried swapping out for new phones and rebooting the CME.

Any ideas?

VSUTech

ASKER

Update:

The disconnects are occurring when calls go to voicemail as well.

José Méndez

What type of connection you have toward the PSTN?

VSUTech

ASKER

It's an ISDN connection

sr75

Sounds like it may be VAD. Make sure that all of your voip dial-peers have the "no vad" command in them.

VSUTech

ASKER

Would VAD all of a sudden become an issue?

Nothing has changed for months in our configuration.

sr75

A similar problem happened to me in the past after it working great for several months.

VSUTech

ASKER

It looks like they do have "no vad" on each

dial-peer voice 100 pots
description Outbound Calling (Long Distance)
destination-pattern 81[2-9]..[2-9]......
direct-inward-dial
port 0/0/0:23
forward-digits 11
!
dial-peer voice 101 pots
description Outbound Calling (Local)
destination-pattern 8[2-9]......
direct-inward-dial
port 0/0/0:23
forward-digits 7
!
dial-peer voice 102 pots
description Outbound Calling (911)
destination-pattern 911
direct-inward-dial
--More-- port 0/0/0:23
forward-digits 3
!
dial-peer voice 200 voip
description Inbound Calling
destination-pattern 2..
session target ipv4:10.2.0.1
codec g711ulaw
no vad
!
dial-peer voice 6000 voip
mailbox-selection orig-called-num
description CUE Voicemail
destination-pattern 6000
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 6001 voip
description CUE Administration
destination-pattern 6001
--More-- session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 300 voip
description *** Auto Attendant
destination-pattern 300
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 301 voip
description D*** g Auto Attendant
destination-pattern 301
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
--More-- !
dial-peer voice 306 voip
description *** Investors Auto Attendant
destination-pattern 306
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 310 voip
description ***
answer-address 310
destination-pattern 310
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 311 voip
description *** Welcome AA
destination-pattern 311
--More-- session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 3111 voip
description *** Voicemail AA
destination-pattern 3112
session protocol sipv2
session target ipv4:10.2.0.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 103 pots
description Outbound Call (International)
destination-pattern 8011T
port 0/0/0:23
!
dial-peer voice 313 voip
description Copy Machine Fax Machine
destination-pattern 313
--More-- session protocol sipv2
session target ipv4:10.2.0.3
codec g711ulaw
no vad
!
dial-peer voice 2 pots
incoming called-number .
direct-inward-dial
port 0/0/0:23
!

ASKER CERTIFIED SOLUTION

José Méndez

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

VSUTech

ASKER

Thanks for the suggestion...

I'm trying to replicate the issue right now but after 25 calls or so I can't get it to disconnect.

Could this have been an issue with the service provider? They have been "monitoring" the line for the past 4 hours or so. I'm still waiting to hear back from them.

SOLUTION

sr75

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

VSUTech

ASKER

it appears this was a service provider issue. I wasn't able to replicate the issue with the additional logging.