If the trunking is working, but the only problem is this delay under certain conditions, I seriously doubt that the problem is specific to the HiPath 4000.
My first instinct is:
Alcatel problem! In the timeframe of HiPath 4000 v4, SIP Trunking was just being introduced. It is quite possible that the Alcatel or HiPath 4000 is just not capable of handling that transaction.
Does the 4K have all RMX hotfixes installed? According to SBCSU (TekTips user), your STMI loadware is up-to-date, but your RMX code may not be up-to-date. The Alcatel may also be lacking some updates.
For this
7-second voice gap problem to be analyzed thoroughly, a Unify BLS engineer would need to start a trace, capture the failure, and analyze the trace data. This analysis process is tedious, requires indepth knowledge of the HiPath 4000 code, hexidecimal output data, and involves the use of proprietary tools to which the field has no access.
It sounds as if you may not be 100% certain HOW calls are routed to the Alcatel, and you should be aware in order to have an opportunity to further analyze the problem.
Is your SIP Trunking being handled by the HiPath 4000 Large Enterprise Gatekeeper (
LEGK) (also known as IP Trunking V2), or are you using Native SIP Trunk Profiles directly on the STMI board?
There is also the possibility that the 4K is using IP Trunking V1, where the STMI board has a "Routing Table" onboard; however, I
think that IP Trunking V1 works with H.323 protocol only.
It has been many years since I worked with IP Trunking V1.
Do not try to guess which method is being used, because all three methods ultimately use a STMI board!!!
Here is how to tell for sure. Perform --> DIS-CGWB for the STMI that is being used as your trunk to the Alcatel system. Is only one STMI being used?
In the top "Global Interface" (GLOBIF) section of the DIS-CGWB output, look at the Trunk Protocol parameters
TRPRSIP, TRPRH323, etc.
ONE of these "TRPR" parameters should have "X" number of channels assigned to it, usually "
30". For a HiPath 4000 v4 system to communicate with another vendor's switch, typically
Native SIP protocol is used, which is the CGWB --> "
TRPRSIP" parameter.
Now perform DIS-GKREG;
Are there any Gateways configured here, such as "GWNO 1", "GWNO 2"??? If so, now perform DIS-ZANDE:ALLDATA; Is parameter "GATEKPR" set to YES or NO?
If NO, then you are NOT using the LEGK to route calls to the Alcatel.
If YES, but there are no Gateways configured in AMO GKREG, then you are NOT using LEGK.
If YES, and there
are Gateways configured in AMO GKREG, then there is a possibility that you are using the LEGK to route calls to the Alcatel.
You can confirm by looking at the LCR routing. DIS-LDAT for the route that handles trunking traffic to the Alcatel. Is there an entry in the "
GW1" or "
GW2" or any of the "GW
x" fields?
If there are no entries in these LDAT parameters, then the Large Enterprise Gatekeeper is NOT being used. Your trunking is being handled by the STMI's Native SIP Trunking Profiles.
If you determine that the LEGK is handling the Alcatel traffic, then re-post here. I will provide additional LEGK info. The LEGK attributes configured via AMO GKREG for each gateway must be configured perfectly for the trunking to work properly. Since the trunks are working except for that one "voice gap" scenario that you described, I doubt that you are going to find any mis-configuration.
For a STMI to support Native SIP Trunking, all trunk channels must be assigned to the AMO CGWB --> TRPRSIP parameter as mentioned previously.
Access the STMI via Web-Based Management. (using Internet Explorer, connect to
Address of STMI>
Login as TRM, with password HICOM using ALL CAPITAL LETTERS (unless password has been changed).
At the top menu bar, click "Explorers".
In the Left Pane, click "Voice Gateway".
In the Right Pane, click "SIP Trunk Profiles"
If the STMI is truly handling the Alcatel traffic, then one of these "Profiles" should have a
GREEN folder, while all other folders are NOT green.
Right-click the Profile with the Green folder, and select "Display Settings".
The "proxy" settings should indicate the IP Address of the Far-End (Alcatel) gateway.
Is the IP Address correct? On this same page, you should be able to see if TCP or UDP is being used. If all of the settings look good, then have a second look at AMO CGWB.
Is the Default Router configured??? If not, perform CHA-CGWB and add the Default Router address. Bad Default Router config can cause all types of cRaZy one-way voice and sometimes NO Voice.
As SBCSU stated, your system's STMI has the best loadware available. You should not attempt to update the STMI's loadware using loadware from a different version of the 4K. The result will most likely be NO TRUNKING via that board!
Good Luck!
