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!

Message Waiting Light not turned ON

Status
Not open for further replies.

0624031980

Technical User
Oct 8, 2009
4
US
I have a particular site that has MD110 PBX using onebox voicemail. Some of the users on this site were complaining about message waiting light indicator turned OFF on their phones. I have done almost everything that are need to be done to get this message waiting light turn ON restored.
I have restarted the program unit for ILCP and ILNP and do even RFEXI. When I did the ICUPI, the printout was INFORMATION SYSTEM UPDATE NOT SUCCESSFUL
IFCIND CHANNEL ERROR DETECTED
IFCIND
2.

Please can someone help out on this.
 
Any messages in ALLOP? Is it serial or IP connected?

Can you post ICFUP etc please?
 
i have had this before:
make records from by print-outs then try;

END DATA----
VMPOE:DIR=xxxx&&xxxx;
VMPOE:GRP=xxxx;
VMFUE:IFCIND=1;
ICFUE:IFCIND=1;
RFPUI:UNIT=ILNP,LIM=1;
RFPUI:UNIT=ILNP,LIM=1;

RFBOI:BPOS=001-0-70; position of NIU !!
RFBOI:BPOS=001-0-70;
IONCE:IODEV=ONEBOX,USER=GICI-1; or whatever you have called it

NOW RE-ENTER DATA-----

IONCI:IODEV=ONEBOX etc....
ICFUI:IFCIND=1,IODEV=ONEBOX,FILLER=48,DFMT=4,UPDFCN=YES,USER=GICI-01;
VMFUI: IFCIND=1,VMF=EXTN2,POFMT=3;
VMPOI:IFCIND=1,DIR=xxxx,PORT=001;
EXECUTED ---DO THIS UPTO DIR=xxxx,PORT=xx
VMPOI:IFCIND=1,GRP=xxxx;
ICUPI;
ORDERED
SPONTANEOUS PRINTOUT

INFORMATION SYSTEM UPDATING SUCCESSFUL
END

 
Bit premature there mdevo, we don't know how it's configured. It might be over ICU board or something. It could be the network or cabling between onebox and MX.

Although I have seen this before and have to remove/reinitiate, but also RFEXI does make it work too. His case RFEXI doesn't make it work.
 
A RFEXI; will not help you solve this issue.

The only way to "kill" a hanging update is to find all the program units of type DIM&DIR in all LIMs, and restart them.

So, find the PU's, program units:
CNPIP:UNIT=DIM&DIR;

And restart them:
RFPUI:UNIT=DIM,LIM=;
RFPUI:UNIT=DIR,LIM=;

You could set the UPDFCN to NO, then you will not have this kind of problem:
ICFUC:IFCIND=;UPDFCN=NO;

Let me know, how it works out...!


///doktor
 
Restarting the PU's "ILCP and ILNP" in addition, would be a good idea...(in the LIM, where the ICU/ICU2/NIU/NIU2 is installed).

///doktor
 
All,

I have tried all the suggested options of restarting the PU's and nothing seems to work. I want to try and reinstall the voice mail board with the parameters, but the problem am having now is that I dont know the position of the board on the LIM and some parameters:
Here is the printout
<?ICFUP;
INFORMATION COMPUTER COMMON FUNCTIONS DATA

UPDATING START TIME IS 01:30

MESSAGE WAITING FUNCTIONALITY IS ALL

INFORMATION COMPUTER EQUIPMENT DATA

IFCIND IODEV EQU RATE DFMT UPDFCN PARITY CCHECK

2 YES
ICEXG=NONE USER=GENERIC

END

The EQU position is not known, RATE not known, DFMT not known and the USER is generic.

Please I need help.
 
Please, am an doing a remote login, I am not on located at teh site.
 

pls send IONCP; and IONPP; you are set as generic not serial

best parnum
 
<?IONCP;
NETWORKING CONNECTION

NODE/IODEV LIM USER TYPE/CON IP PORT PROC

END

<?IONPP;
NETWORK PORT CONFIGURATION DATA

EQU IP GATE MASK ETHERNET

001-0-60-4 143.25.18.1 143.25.0.1 255.255.0.0 00.80.37.AF.0E.12
END

The IP address in there is for remote login, not for the voicemail.
 
are you sure, the MWI check box is ticked in the onebox software administration?

In onebox > administrator > mailbox numbers > right click "edit" > features > "set MWI" & "empty" check boxes.
 
What type of OneBox are you using? 4.1 or 4.2?
The code for 4.1 is 770 and for 4.2 it is 790.
You can see the at the OneBox main program.
If it is 4.1 there are 3 patches that could be needed...

///doktor
 
Try to post this info, here:

1.
VMGEP;
IPEXP:DIR= the extension numbers from the VMGEP;
2.
IPBOP:BPOS=ALL;
One of these IPLU's carries the IP lines to the OnBox.
3.
Check my last post.
4.
Check Monrovia's post.

With these 4 hints, you should be near the goal...



///doktor
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top