Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco CUSC calls to Avaya aura vdn/vect - hears announcement then gets to agent and can't hear

Status
Not open for further replies.

beckyanne06

Technical User
Jan 19, 2009
5
0
0
US
Hi All- We (Avaya Aura 6.2) have recently been acquired by a company using cisco CUSC and both company's have multiple offices internationally.
We are connected by H.323 ISDN lines. Direct Avaya/Cisco extension to extension are working fine.
The problem we are having is when Cisco calls an Avaya VDN⇒vector with announcements to agent. The calls get to the agent but can't be heard in either direction. And it is intermittent.
The vector traces look the same whether the call goes through or not
vect_903_1_b3a8cm.png

vec_903_2_nrpt42.png


The only trace where I can find any difference is in the station trace--- this call could not heard either direction.
trace_station_-_no_go_ue20oy.png


We had to update our codex set for the ip-network-region to include G.711 for the Cisco calls to hear the announcements.
codex_1_y4peqe.png


The one thing I noticed during testing was when the call went through the ringback on the agents phone could be heard by the cisco call. I added a " wait-time 10 sec hearing ringback" in the vector after the announcements when I noticed this. Still no luck.
I appreciate any help-- this is affecting our internal helpdesk and another site that forwards it's customer calls to another office. We have created work a around that send the calls through POTS for the customer calls. And for our internal operations we removed all announcements and that seems to work. Neither are great fixes.
Becky
 
Are you sure all those codecs like 729b and 723? Can you try with a different codec set with just 711?
 
What's weird is all the calls to and from Cisco and Avaya use the same codex set as the one we are using now and work fine. Even before we added the G.711
Though I think that may be our next move -- create a new codex set with G711 first. We still need some of the G729's - because of the international connections. I will follow up and let you know if this fixes it.
Thanks for the suggestion.
B
 
This sounds like a problem with the IP-Network-Region. As an Example - region 1 not being programmed with settings for communication with region 10.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top