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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HiPath HG3570

Status
Not open for further replies.

jschnarkey

Technical User
Aug 26, 2015
70
US
Hello,
I did not know what the two HG3570's were for in my system and deleted them so that I may re purpose them for a new trunk group. All heck broke loose here and a big lesson learned. Good thing I had a sys dump of the config from a few months ago.
My problem now is that XPressions MWI cancell does not function in my HFA phones. TDM, sure but HFA, no way. Lights come on and stay on no matter what.
Could this be related? It is obviously the one thing that changed in my system.
 
I would not expect that to be related. HG3570 provides the VOIP payload between the 4K shelves 1-15 and the IPDA shelves. If you only have IPDA shelves with no LTUs 1-15, you don't have an HG3570, don't need one. You don't need one if you don't have any IPDA either.

 
You make a valid point. I do however have shelves 17 - 22 and the problem started at about this same time. I'll now take a closer look at the affected phones and see what shelves they are built on. I did narrow it down to HFA.
The Xpressions is tied to the OSV which in turn has SIP trunks to the 4K (4 STMI's) SIPQ but like I say, TDM works and HFA, the lights come on and never go out. Nor the envelope on the screen. (OS40 HFA's)

Perhaps I need to look elsewhere but just though I would see if anyone had any thoughts.
I'll dig a bit deeper and try to put some more facts on my notepad.
 
I don't know your particular setup, but I know for us, we have one building that's on a 4000 V5 and another on a 4000 V6. They share Xpressions. They are tied together with an IP trunk. We had to make sure that the V5 (with Xpressions) could see the V6 by building them in the WABE. Otherwise MWI would fail.

In this case, x8167 is on the V6. I have to put an entry on the V5 PBX so that Xpressions can send the MWI over trunk group 100 to get to the V6

Code:
  | DIGIT INTERPRETATION                   VALID FOR ALL DIAL PLANS            |
  ------------------------------------------------------------------------------
  |                 |    CALL PROGRESS STATE     |NODE/DIGIT| RESERVED/CONVERT |
  |      CODE       |            1 11111 11112 22| ANALYSIS | DNI/ADD-INFO     |
  |                 |0 12345 67890 12345 67890 12|  RESULT  | *=OWN NODE       |
  ------------------------------------------------------------------------------
  | 8167   - 8168   |. .**** ***** **... ..... .*| STN      |                  |
  |                 |                            |          |DESTNO 100        |
  |                 |                            |          |DNNO    0-  0-100 |
  |                 |                            |          |PDNNO   0-  0-100 |

This was done by CHANGE-WABE:8167&8168,100,,;

Again, not sure if this applies to you, but it definitely did for me.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center
 
There are some strange things about MWI, but I will preface that with I do not know Xpressions - we use AVST, and I am not exactly sure what the weird things are....

I know that on my 4K, with AVST CX-E, we specifically have to use analog lines to do the activate/deactivate on the MWI. There were some things like permissions for MWI like the same port that set the light ON had to be used to set it OFF, and there were limits on how many MWI commands are allowed to happen on a digital port that do not affect analog ports. As I said I do not know if any of this relates to Xpressions.

In my system I have one special analog phone on my desk that is set up to be able to affect MWI - don't ask me how B Box set it up, but when I dial out from it it only gives out the Number 4 as the ID of the calling party.

On that phone, I can dial *530 XXXX # to shut the light off, and *532 XXXX # to turn the light on. You could look in WABE and see if those 2 digit strings are set up, and if so you could try keying them in on an analog phone and see if they affect the message light on an HFA phone just for experimentation purposes.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
Yea, 4K to OSV is netroute 100 for us in wabe and like I say, TDM is working and HFA lights are going on. Calls are routing quality is good etc. Very strange. I am at this moment ascertaining what shelves the affected phones are built on by culling through the work orders.
I'm sure it has something to do with some programming I did but I need to track it all back and take better notes hence forth.
 
If it gets really deep, you may wish to take a look in Xpressions.......

Open XPR Monitor, then under <Preferences>/mta/Edit Settings. Look at the Global Journal tab. Thinking you will see MWI failures here.

You can also look at the logging to look for problems in real-time. Change the Module to mta and the Topic to <All>. Check the boxes under Displayed Data to get as much detail as you want. Just keep in mind that the more you display, the slower Xpressions will be in real-time, so you don't want to keep it like that for a long time. You may wish to set it up to log to a file. Just right-click on the log window and select Properties. Go to the View tab and tell it where you want the log file. Hit OK. Then when you're ready, right-click on the log window and select "Log to File". Unselect "Log to File" when you think you have enough data to look at. I highly recommend "Notepad ++" for viewing log files.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center
 
Well what do you know...I also have these codes built
I'll try this as soon as I get to the Hospital.


DIS-WABE:GEN,*532;
H500: AMO WABE STARTED
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| *532 |. ....* ....* ..... ..... ..| MBON | |
------------------------------------------------------------------------------

AMO-WABE -111 DIALLING PLANS, FEATURE ACCESS CODES
DISPLAY COMPLETED;
<dis-wabe:gen,*530;
DIS-WABE:GEN,*530;
H500: AMO WABE STARTED
------------------------------------------------------------------------------
| DIGIT INTERPRETATION VALID FOR ALL DIAL PLANS |
------------------------------------------------------------------------------
| | CALL PROGRESS STATE |NODE/DIGIT| RESERVED/CONVERT |
| CODE | 1 11111 11112 22| ANALYSIS | DNI/ADD-INFO |
| |0 12345 67890 12345 67890 12| RESULT | *=OWN NODE |
------------------------------------------------------------------------------
| *530 |. ....* ....* ..... ..... ..| MBOFF | |
------------------------------------------------------------------------------
 
Xpressions setup as IP or ISDN will not need to use the MBON or MBOFF codes, it just sends an IP or ISDN message.
Analog integrated voicemail systems do require the MBON and MBOFF codes to be present.
If your XPR is not getting lamp on/off then you could be missing the RICHT PM
If RICHT PM is set to 1 for example then the phone that gets the lamp needs to be set to PMIDX=1
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top