05-24-2022 02:18 AM - edited 05-24-2022 02:52 AM
Greetings,
i'm experiencing some audio quality issues on my PRIs, started recently and nothing changed on our enviroment - below is what is experienced and Telco says they see no errors on their side (they reloaded and still the issue continues):
- Crackling noise on inbound calls (none on internal calls)
- When far end is silence, sounds like they're watching a TV though they report to be alone in the room (more like crossed lines when there is silence on the call).
Reaction:
- First rebooted the GW to no luck
- Added and removed commands below on voice ports, no change:
compand-type u-law
bearer-cap Speech
**When we add on all voice-ports we are unable to make calls
Configs:
aqm-register-fnf
!
card type e1 0 0
card type e1 0 1
logging buffered 10000000
no logging rate-limit
enable secret 5 sdsdsds
!
no aaa new-model
clock timezone SAST 2 0
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 E1 0/0/1
network-clock-select 2 E1 0/1/1
network-clock-select 3 E1 0/1/0
network-clock-select 4 E1 0/0/0
controller E1 0/0/0
pri-group timeslots 1-31
description 0111114000
!
controller E1 0/0/1
pri-group timeslots 1-31
description 0111114000
!
controller E1 0/1/0
pri-group timeslots 1-31
description 0117574000
!
controller E1 0/1/1
pri-group timeslots 1-31
description 0111114000
!
ip ssh time-out 60
ip ssh authentication-retries 2
ip ssh version 2
!
voice-port 0/0/0:15
translation-profile incoming ForDNIS
timeouts interdigit 4
description 0111114000
bearer-cap Speech
!
voice-port 0/1/0:15
translation-profile incoming ForDNIS
compand-type u-law
timeouts interdigit 4
description BACKUP PRI - 0117574000
bearer-cap Speech
!
voice-port 0/0/1:15
translation-profile incoming ForDNIS
timeouts interdigit 4
description 0111114000
bearer-cap Speech
!
voice-port 0/1/1:15
translation-profile incoming ForDNIS
compand-type u-law
timeouts interdigit 4
description 0111114000
bearer-cap Speech
Solved! Go to Solution.
10-01-2024 02:00 AM
Issue was on Telco side, they had to move the PRI to a different port on their end and that fixed the problem.
10-01-2024 02:00 AM
Issue was on Telco side, they had to move the PRI to a different port on their end and that fixed the problem.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide