Hipath 4000 V5 RMX R.1.7.28 / UW7 R1.3.3 - IP Phones from my IPDA are not functioning properly

[Hertz]

Hello Gents,

​

We update our system to this new release. We have our main system and IPDA. Upon updating the system by swapping the HDD. Main system is okay but the IPDA has some abnormalities from the IP PHONES. All are HFA Phoens but when dialing from the phone. the tones from the keypad sounds like a SIP version. there is a beep tone everytime you dial. And we notice as well that the outbound calls are very robotic sound and distorted.

Any one here has the same issues and resolved?

thank you

Best
Hertz

 

[Moriendi]

There is an optional patch to activate, which disables key clicks on HFA phones. You could try that.

act-patchpt,s,39;

You will need to restart any HFA STMI cards.

Don't know about poor call quality. Upgrade should not cause that. Did you put the latest loadware on, as well as the latest RMX RLC? Because a loadware hotfix will exist for sure.
Sounds like your network but I suppose you will say you had no problem prior to upgrade.

 

[donb01]

Hey Moriendi, is there a similar patch for V7R2? I have that initial beep when dialing on-hook (OS40/60 HFA), and while it does not bother me or anyone else normally, when I use OSPE with my headset it absolutely will rip my head off if I forget to hold the headset speaker away from my ear. I remember going through all the ZAND parameters years ago, but I never found anything that implied it would shut that off. I complained to TAC (indirectly) and the response was basically "we have no idea what you're talking about."


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Hertz]

@moriendi no loadware patch has been initiated yet.if possible can you share to me on how to check the status and load the patch? i hope my boss can still download the latest patch for this system..

and will try also the act-patch command.

thanks man.


Best
Hertz

 

[Moriendi]

Don, in V7 it's a zande optfea. Not sure it will help, it's to disable key clicks on HFA phones, not ear deafening beeps, but if you want to try, cha-zandeptfea,a,39; You will need to restart the HFA card afterwards.

Hertz, to check the loadware you have, you need to list the file header for the files used to load the STMIs and NCUIs. STMI/NCUI loadware is released as a pair, you can update one without the other but it's not recommended (due to the HG3570/HG3575 use case. For STMIs used only for phones and trunks, it's not so important).

Last released for V5 was LW 28.007-004. You can see that in clear text at the start of the file.

Below commands will list the headers. See how near you are to 28.007-004. Fairly close I think but not quite there.

sta-list:"ds:apsp/ltg/lga0/pzknci40",,200,t;
sta-list:"ds:apsp/ltg/lg98/pzksti40",,200,t;

If you are able to download the hotfix, it's just a case of replacing the files on the HD, and Assistant, Expert Mode, Gateway Manager can be used to push the update. Make a refresh board list from GW Manager or it might not notice you have updated the loadware. Backup the old files before you replace them (or make sure you have a MO DDRSM copy of PDS).

 

[Hertz]

@moriendi

since the issue also is on the outbound as well. is there a way to run a check slso on for these carda? what command in sta-list? bcoz my boss manage to escalate this directly to unify and then sent us a loadware file that needs to be load as per them. the filename here is pzfdue10. dat

Best
Hertz

 

[Moriendi]

DIU loadware is in lga1 so

sta-list:"ds:apsp/ltg/lga1/pzfdue10",,200,t;

And compare that output from your 4K with the header in the file you were sent. If it's the same - no point changing.

I don't see any newer loadware for the DIU in the last released HF for V5. But loadware from a newer 4K, V6, V7 etc would also work.

 

[adibv]

Hi.

IP bad quality is pretty hard to investigate.
Additionally to STMI/NCUI LW check, you may check HISTA for F5749 (board LW req.) error messages and F5915 (Bad IP qual.) error messages.
In HISTA check also F4066 error messages(Byte 0 =1B -> CP_GK_GW_TMP_NOT_AVAIL and CC:15362). This could lead to LAN issues.
Check param. GWNAVAIL (on CTIME:TYPESWU=CP2) and try to decrease it (usually is set to 5) and observe the behavior.

A wireshark trace (you need local mirror port) could be helpful together with GW trace fro GW WBM trace/logs page.

Check if you have latest SW ver. for HFA devices (synchronized with V5 sys ver .... check release notes for devices sw. ver.)
If you upgrade to unsupported device SW ver. you could damage the device -> DERT

You said "we notice as well that the outbound calls are very robotic sound and distorted".
Outgoing calls over which trunk/route: ISDN (DIUN) or IP (STMI) ?
There is an ISDN trunk connected directly on IPDA to provider or ISDN trunk is connected directly to main sys and not to IPDA ? (in this case calls being routed over NCUI to main sys and than to ISDN trunk) ?

Be careful with boards LW upgrade to be synchronized with V5 sys version.
If you upgrade with a LW from a newer ver. than V5 or unsupported, you might end up to have an unusable board/trunk.

Latest boards LW supported on V5R1.7.x:
DATE : 12/11/13
For STMI : PZKSTI40 LW 28.007-004
For NCUI: PZKNCI40 LW 28.007-004

For DIU boards (ISDN trk) on V5 R1.7.x:

Part NO Fct. ID
DIUT2-E1 Q2226-X200 1 pzfdue10.O1.018 09/21/12
DIUT2-E1 Q2226-X200 2 pzfdue10.O1.018 09/21/12
DIUT2-T1 Q2226-X200 3 pzfdut10.O1.012 07/05/12
DIUT2-T1 Q2226-X200 4 pzfdut10.O1.012 07/05/12
DIU2U-B Q2216-X 5 pzfdunbk.N1.026 11/10/09
DIUT2-T1 Q2226-X200 4 pzfdut10.O1.009 06/14/10
DIU-N2 Q2196-X 2 pzfdca20 L1.031 08/26/11

 

[donb01]

@Moriendi - Activating patch 39 DID stop the key beeps and that really loud annoying first beep. I flipped it yesterday, and hadn't intended to reset the gateways until after I pushed out new loadware, but at least some of them must have reset overnight and I do have quiet today. I have one user that reported it but didn't care either way, another that said they noticed it during a conversation with me this morning and could care less, and of course a couple old ladies in a call center that should have been gone years ago that don't like it because they NEED those beeps when transferring calls. Church is out so far unless tons of people complain. I assume if I have to flip it back that I just change the "a" to a "d"??

THANKS!

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[Moriendi]

Great!

Yes change the "a" to "d" to deactivate, no hassle.

Interesting that it was working this morning (and was not working immediately after you changed zande?). Did you check hista for stmi restart or look in the evtlog of the stmi? Maybe they changed the behaviour of it. Sometimes the behaviour is changed but not the documenation. I will try it when I get a chance, just out of curiosity. What is your stmi loadware, phone model, phone firmware?

Yes I'm familiar with old ladies like that. Best to avoid!

 

[Hertz]

@moriendi,

We did not yet load the LW and upon checking the ussu. We notice this.

Would this be our real problem? or is it normal?



Best
Hertz

 

[Moriendi]

That's normal. You can check the LW on the card by browsing to it directly or through Expert Access, Gateway Manager in the Assistant and you can see the LW variant in bottom of the window. If it's the same as the version on the HD (use previous sta-list command), you are OK.

The SIU tones will be correct already or users would be complaining, but you can push the files over with exec-ussu:ncuiload if you want, then dis-ussu output would change. But this will not be causing your problem.