One-way spe ech - VTRK only for CFNA 3

[curtismo]

Have a strange problem following upgrading of one of my CS1000E systems to 7.5 over the weekend. We have a second system with 6.0 and found out late yesterday that calls from the 6.0 system to the 7.5 have one-way speech on the H.323 VTRKs - but only on CFNA to the Call Pilot system on the 7.5 system (callers can't hear the VM prompts, but speech in the other direction is recorded). No issues if phone is CFW to the VM system, or if the call does a BUSY hunt to VM (but not a CFNA hunt).

We have the 6.0 system upgrade to latest CS and SS patches to prepare for an Avaya support call, but am open to any suggestions for this odd issue.

 

[Triton101]

we had the reverse (transfer from CP to user), went with SIP trunks and problem went away.

we found that the Audio manager portion of the sig server was not sending the "open stream" in one of the directions (caller or callee) when H.323 was used.... worked fine with SIP....

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

Unfortunately, we have no SIP licenses, so I'm SOL with that workaround. Did you open a ticket with Avaya on this issue?

 

[Triton101]

nah, we went through patching everything on both ends even the CP and gave up since we had 200+ sip trunks, we were sniffing and trace logs on the servers.... once we found the workaround we gave up on the fixing the h.323 part....

if you look at the sig server log files, it might have some indication of a problem with the media stream. but you would have to track it by time of the call being made....

diff scenario in your case though... so there might be a patch (now or in the future?)....

the other thing i heard was NRS 6.0 talking to ta 7.5 endpoint having issues....i think the AVAYA recommended config is to have NRS be 7.5 if you have a 7.5 system.

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

Avaya tried a patch today; didn't work. Yook some TLAN sniffs on the MGC that has the MGate card in it but all I could see was that I had one-way audio from the phone on CFNA and two-way audio on HUNT to VM.

Since I can duplicate it in-house (IP phone homing off the 6.0 server) we may have an easier time looking at the SS logs. I guess I should ask what particular SS log were you looking at? I'm guessing I should be looking at the Sig Server that has the VTRK app.

 

[Triton101]

yup, whichever the DSP resource is tied to

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[cypher0]

Are these OWSP issues going through the same DSP?

 

[Triton101]

can't find our old logs, but here is something similar, you might be able to match up the call times with the error messages (i think its from the core apps log);

vtrk: (ERROR) tNPM: npmSendOLCAck: no rx channel found

(i think..... over a year ago...)

Open logical channel messages refer to the media streams for h.323 from what i remember.....



__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[Triton101]

also, try to CFNA a phone on the 7.5 system to another phone (instead of VM) and see if you get 1 way audio when you pickup the second phone, once the call CFNAs from the original phone (might be easier to track also if it has the same issue)

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

Tried the last suggestion multiple ways, and I have normal two-way speech. Even to the point of building a small ACD queue with message waiting service, and placing a ACD agent phone on the same cabinet as the Call Pilot MGate card; we had two-way voice.

ELAN traces were taken on the sig servers on both ends of the VTRK this morning by the vendor techs to send to Avaya. Still waiting (sigh).

 

[edgyeddie]

We have a similar problem with BCM sites that cfna to call pilot on cs1000e rls 7.5 h323. We get NO SPEECH PATH. This is since the upgrade from 3.0 to 7.5 and we have 2 tickets that have been escalated up (One BCM and One cs1000) They say its a timing issue when cfna to call pilot (cfna to a phone works fine) Avaya is still trying to figure out who needs to write a patch BCM or CS1000 But they contend that h323 trunks dont work well with the newer releases

 

[curtismo]

Last update is that the issue has been sent to Avaya design. As of now have not heard a thing from anyone.

(Avaya design team: Ok, we didn't have problems under 6.0; what did you change in 7.x to cause this to occur?)

 

[Triton101]

lots of issues with 7+, when it came out, M2216 would disable its TN if the handset (or heaset) was not plugged in for a couple min.

things that worked before, did not on 7+..... strange....

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

Update -

There is no update.

Avaya says that an OLC (Open Logical Channel) is being sent from the 6.0 system to the 7.5 system, but no OLC is sent from the 7.5 system.

They are looking at the OLC not leaving the 7.5 system or the possibility that a subsequent command from the 6.0 system that has a null in it is causing the 7.5 system not to even try opening the media path.

 

[Triton101]

Keep us posted and thanks for the update.

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[curtismo]

Of course this could end up being a moot point when we upgrade the 6.0 system to 7.5 in 2 1/2 weeks...

Although I have 15+ MG1000B 6.0 systems hanging off of the current CS1000E 6.0 system. Would be my luck that they will have problems transferring to the 7.5 after upgrade.

 

[spanton]

Hey Curtismo...did you every get an answer on this issue? I just updated one of my site and I am having this issue now.

 

[curtismo]

Hmm, don't know how to answer this, since the provider really didn't tell us what they did - until I asked - again.

And after checking out what they did I am finding the setting enabled - when supposedly they disabled it.

Anyhow, they say the setting they changed was to disable H.245 tunneling on the Sig Servers on both sides of the H.323 link.

But the setting is buried so deep you have to use a vxShell command to set it.

 

[bc1111]

Had the same problem after upgrading two switches to 7.5.
Avaya came out with a new linux service pack with a patch that fixes the problem.

 

[NortelAvayaBlue]

Had the same issue after I upgraded to 7.5 co-res. The calling site was still at 6.0.

turning off h.245 tunneling on both systems and a sig serv reboot on the 7.5 cleared the issue. There is NO patch yet written for this as Nov 5th 2011.

I shared this post with Avaya TAC, and they gave me the following instructions.

log into the sig serv hosting the H323 trunks and type vxShell.

then stat tunniling and disable tunneling.

For Rel 7.0

1. First check the state of H245Tunneling is ON or NOT, give

vtrk npmH245TunnelingState

Note:
0-Disable
1-Enable

2. To disable H245Tunneling , give

vtrk npmH245TunnelingDisable


For Rel 4.5 and 6.0


1. To check the Tunneling status Login to vxshell, give pdt>vxshell

vxshell>npmH245TunnelingState


2. To disable H245Tunneling

vxshell>npmH245TunnelingDisable

Now if these commands dont work all try this:

vtrk q931MultiplexingEnable to turn H.245 on < - for rls 7.x
vtrk q931MultiplexingDisable to turn H.245 off < - for rls 7.x