No Ringback Tone

[TelcomAdmin]

I have a Prologix and an S8300/G700 connected together VoIP byway of a T1 VPN internet connection. The setup allows for 4-digit dialing between sites.
Problem - When dialing from the Prologix to the S8300 the calling party does not hear ringback tone but at the distance end the phone rings normally. This is an intermittent problem that recently surfaced.
In this scenario which switch provides the ringback tone? The Prologix is using an IP Media Processor and the S8300 is using a DS1 card. Any help would be greatly appreciated.
Thanks -

 

[NX01]

Do you have Silence Suppression on? Maybe there isnt enough bandwidth for the call. The system will suppress the ringback to conserve bandwidth.

In the future everything will work...

 

[Konri]

Set the same codec on both sides.

 

[TelcomAdmin]

Silence Suppression set to off and codec same on both ends.

 

[NX01]

What does the Signaling group look like for the Prologix?

In the future everything will work...

 

[mgoston]

In my experience if you find any new or intermittent problem on networked 8700s load the latest version of firmware. Avaya is constantly making updates to the system. Sometimes an intermediate patch will fix current problems.

 

[TelcomAdmin]

Group Number: 69 Group Type: h.323
Remote Office? n Max number of NCA TSC:
Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 69
Supplementary Service Protocol: a
Near-end Node Name: olyclan Far-end Node Name: seas8300
Near-end Listen Port: 1720 Far-end Listen Port: 1720
Far-end Network Region: 2
LRQ Required? n Calls Share IP Signaling Connection? y
RRQ Required? n
Bypass If IP Threshold Exceeded? y
Direct IP-IP Audio Connections? y
IP Audio Hairpinning? y
Interworking Message: PROGress

 

[BuckWeet]

sounds like a one way voice path issue.. when you get connected, can you hear each other??

 

[TelcomAdmin]

When connected both ends can hear each other.

 

[Konri]

Try to set the same codec in Network Region 1 and use Network Region 1. For others use Network Region 2 and next regions

 

[BuckWeet]

I'd make sure you have the latest firmwares on the medpro boards..

If that doesn't work, call TSO.. I just ran into an issue with a S8700 2.0.1 ip trunked to S8700 1.3.1.. If you had out-of-band dtmf set, the 2.0.1 side IP phones would hairpin to the medpro board of the switch.. Had to get a patch to fix it..


BuckWeet

 

[NX01]

I thought of that to Buckweet but it isnt on the signaling group...where else can he change that? On the far end signaling group possibly?

In the future everything will work...

 

[TelcomAdmin]

Thanks for your assistance. Here's what I have done so far. According to Avaya, the ringback tone is generated from the near end switch (my Prologix), so I upgraded the Prologix's Medpro & CLAN firmware. The problem resurfaced a few days later...grrrr. With the problem present I did a list trace and noticed a "denial event 2308: selected codec mismatch." Does anyone have any further info on this? My codec settings are the same on each switch, so why the mismatch??? But I did find that the UDP port range were not the same on each switch so I correct this. This seems to have fixed the problem for now.

 

[BuckWeet]

That could have been the whole issue..

 

[BuckWeet]

Not sure what you use, but I use 16384 to 32767

If you want to use RTP header compression on cisco routers, you need to use that port range..


BuckWeet

 

[TelcomAdmin]

My port range is 2048 to 3047 and routing is provided by a Checkport firewall.

 

[TelcomAdmin]

Grrrr...it's back. Worked fine for 1 day. Codec on both ends set to the following, is this acceptable?

IP Codec Set

Codec Set: 2

Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.729A n 2 20
2: G.729 n 2 20
3: G.711MU n 2 20
4:
5:

 

[NX01]

TelcoAdmin, what is the HW and FW version of your medpro? I just updated mine and it said something about your problem...maybe

Firmware Vintage 92 provides the following fixes and enhancements:

Firmware Vintage 92 was designed to support new functionality introduced in
Communication Manager 2.1. Firmware Vintage 92 is also compatible with all
previous releases of software that support TN2302AP IP Media Processors.

Firmware Vintage 92 corrects some incompatibilities between FV90 and
Communication Manager 2.1 that could cause one-way talk paths.

Previous versions of TN2302AP HV11+ firmware (pre Firmware Vintage 78) had an
echo cancellation algorithm highly maximized for full duplex operation and
tailored for electrical echoes. Although this worked well with electrical
echoes, it did not always provide for adequate control of acoustic echo from
speakerphones. Firmware Vintage 78 introduced a modified suppression
algorithm which provides improved control of acoustic echo from
speakerphones.

Firmware Vintage 92 further enhances echo cancellation:
- Provides improved echo control during initial training
- Provides quicker initial response to speakerphone echo
- Improves control of very low level speakerphone echo

Firmware has been modified to prevent no/one-way talk paths that were caused
by inaccurate DSP load values.

Firmware has been modified to correctly report round-trip-time and packet
loss statistics to the RTCP Monitor Server. Additionally, IP information was
missing from some RTCP VMON packets. If the RTCP Monitor Server was
configured to generate SNMP traps based on bad network conditions, faulty
statistics could result in false alarms in Communication Manager.

TTY detection has been enhanced to reduce the likelihood of incorrectly
entering TTY mode in the presence of tonal background noises.

In the future everything will work...

 

[TelcomAdmin]

Problem fixed. Loaded S8300 server patch 02.0.110.4-5619.tar.gz.

Thanks all for your help.

 

[chuck14]

Hey TelecomAdmin why did it take you so long to fix the problem. What kind of Admin are you, old school.