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!

Register Log in
  • 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!

IP Office 500 voicemail cuts out for 8 seconds 1

Status
Not open for further replies.
ChrisKelly304

ChrisKelly304

Programmer
Dec 7, 2010
86
US
I have an IP office 500 v2 with the latest version 6 of voicemail pro and the ip office os. When listening to the system attendant or anything involving sound on the phones or headset, the voice cuts out for 5 to 8 seconds. This did not do this on version 5 of the OS. This is a version 6 related problem everything else is the same. It is not flow control issue, I have tried 3 different pc's we have changed the ip 500 unit out twice. I saw someone else had this same issue but it didn't seem like it was resolved. We have a gigbit cat 6 lan with cisco enterprise switches. This is not a speed issue. The voicemail pro pc has no virus protection, no firewall, no screensaver, no themes no background working threads. We have gone to extreme lengths to ensure that there is no networking issues. I do not think this is a network issue only because the sound comes back after 5 to 8 seconds of waiting. This doesn't happen all the time. We even when one step further to prove it is not network related. I made sure that the only two items plugged into our network were the ip office and the voicemail pro pc. This problem still happens even if the they are the only two pieces of equipment plugged into the switch. I am at a total loss. I have tried everything I know in the networking world to fix this issue. I am hoping someone has some ideas........

Thanks in advance

Chris
 
Sort by date Sort by votes
So now it works ?

Man i am good :)


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
Good to hear it's fixed, but that mistake really should stop it working completely or not at all. A new "feature" to add to the list :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Upvote 0 Downvote
I just booted the old unit to see why it did it also. I had the same ip address in both spots. I thought initially that it would act like a backup domain as a fail over but obviously it doesn't. That is why both units didn't work. Now I know I really appreciate everyones help on this. I knew it was somthing that I did wrong just wasn't sure what it was.
 
Upvote 0 Downvote
If you put the backup and primary voicemail server the same ip address you can duplicate it for sure.
 
Upvote 0 Downvote
Just give tlpeter some link loving....he likes it :)

(Hit "Thank tlpeter for this valuable post" on one of his posts)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Upvote 0 Downvote
Well be very careful when you key in a voicemail server ip address. Any character or the same ip in the secondary can ruin your life for 8 months. I really appreciate the help my frustration level was way up there on this issue. Thanks for everyone that posted a response to this issue. I am very relieved it is over.
 
Upvote 0 Downvote
ok Matt is seems like I was not clear in my last 80 posts.
Click to expand...

No - you simply didn't do what was suggested, and ended up going round the houses to resolve an issue.

A structured approach to fault finding works wonders...

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
He didn't seem to get the (pink) hint. So I did.
Click to expand...
Thanks.

@ChrisKelly304, when you had defaulted the system you would have found out that it had worked straight away :)

That is why i told you to default it.
Sometimes things just slip in to the system and are not noticed.



When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
I did the new ip office I over typed the ip address. The old one had both ip addresses the same that is why it did it on both boxes. I had to set the voicemail pro ip to get the voicemail to work just so happened I screwed it up twice in a row. The new box back on thursday was factory setting. I had to find the cause of the problem and if you put anything wrong in the backup voicemail server ip it will fail like this. I had a structured approach it didn't work because one ip setting was incorrect. Something I think I said from the start it being a configuration problem not a networking problem. I did what you suggested when I ordered the new box and received it on thursday it didn't work because the backup voicemail ip was screwed up. I knew from the beginning it was my fault just needed to know what it was. Just happened that peter gave me somewhere to look rather than telling me it was my network.
 
Upvote 0 Downvote
Chris, be careful you don't alienate the people who try to help you on here. I have no doubt you will be back given your support setup or lack thereof.

We can only go by experience and this problem screamed network issues from the start, as we have seen such things many times and that's what it tends to be. It's also the first time I and probably anyone here has seen this kind of issue caused by an address mistype (it would normally not work at all or just work, not only go off when buttons are preseed in an attendant).

So saying you were right all along, and suggesting all we can do is say "network" will not do you any favours.

Now go and enjoy your IP office and bask in your Cisco network magnificence :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Upvote 0 Downvote
When you have a default box then the voicemail is set to embedded.
You only had to change it to vmpro and left the ipaddress to 255.255.255.255
It would have found the vmpro server :)
But it works now and a lot of people will never forget.
I am actually trying it on an IP500v1 now to see what happens.


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
A working stand alone box not on my network doesn't help me in any way. I am sure that would have worked leaving all the ip addresses alone. That doesn't help me I knew the boxes were not bad after I received a new one. I knew it was a configuration issue that is what I said from the beginning. So setting it back to factory would only piss me off more that it worked. I needed to make my configuration work and without knowing where to look factory default or not that would have never worked.

The fact of the matter is that not one person knew where to look for something like this. Not one person was even close to the right place until the end. There was not one post talking about configuration other than network configuration on the lan cards. I have no problem admitting when I am wrong about sending someone somewhere they should not go. A little humility is good. The fact is that I would have still had this problem until we figured out what setting was wrong in the configuration. That setting eluded everyone for almost a week now it is solved.

The truth is the software should never let you put anything in there that would screw it up, the routes are that way, you get a flashing red X if you put something in there that won't work. I admit I screwed the config up said that from the beginning. Now I know what was screwed up and that is all that matters.
 
Upvote 0 Downvote
What was entered in the backup voicemail field?
Perhaps i can log this with Avaya?

When i entered 0.1.0.0 then i get the red cross so there is some check on it.

I have tried twice the same ip but for me it worked on the ip500v1.


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
Chris, we only go off what you tell us, " This did not do this on version 5 of the OS. This is a version 6 related problem everything else is the same" ...not true if you had told us you had been changing the vm server address before it hapened that would have been helpfull, also we asked for traces and when you finally did the trace it revealed the issue, it's almost as if we knew they would help :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
Upvote 0 Downvote
Also an upgrade only would not have this issue because the backup vmpro server is from 6.0 and up :)

We are not attacking you but questions are asked with a reason.
For us the ipo is a daily job so we see a lot of strange issues or bad programming.
This issue is probably new for everybody.


When you pay peanuts, you get monkeys!

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
Not trying to alienate anyone here just said from the beginning that I didn't think it was the network. As far as your comment about my lack thereof. Well I set the ipo up without ever seeing one in two days no knowledge and no help or tech support. Not one post on here to ask any questions at all. I don't think that is too bad. I messed up one ip address and it screwed the system up in a way that not one person knew where to look until over 100 posts later. The system should have never allowed this to happen. My ignorance caused the problem I had no idea that the backup voicemail was not a failover like I thought it would be. If it failed I wanted it to go back to that server and try again. I thought that would would work but it didn't. I admit I screwed it up. This is my opinion but it is a software bug. This should never have happened just messing up one ip address. I agree it should have worked or not worked. I am sorry for being an ass about this but I tried too many things before I even posted this. This ipo had me ready to just throw it in the trash. My temperament was not at it's best because of my level of frustration over the ipo not working.

Again I thank everyone here for their help especially peter he pointed me in the right direction. My only wish is that it would have happened on thursday :) But now everyone knows that you cannot do that and you are right there is not one person that will ever forget this.
 
Upvote 0 Downvote
Peter what you have to do is make the voicemail ip both the same. Mine doesn't have an error when I put a 1 in it. But both ip's set the same address and then use two cell phones call the attendant when it answers let it play then press 0 to rewind the attendant on both phones you have to keep doing it but eventually it will stop playing the attendant message for 5 to 8 seconds. I put it back just a few minutes ago and it does it. I can reproduce it at will now. I have the 0 return to the main attendant message and mine is a wav file custom gretting. It depends on the network activity but it seems like the more traffic the easier it happens. Press 0 on both cell phones at the same time that seems to make it fail faster. I have a spare version 2 that does it as well :)
 
Upvote 0 Downvote
Well I am glad I could help with a new issue. I really do appreciate you guyes helping me. I am just glad it is fixed.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

4thright
  • Question
IP Office 500 v2 - T1 Trunking
Replies
14
Views
689
derfloh
derfloh
telecomgear
  • Locked
  • Question
Working IP Office 500 v1 4.2 suddenly cannot dial out on PRI. Call come in fine.
Replies
8
Views
615
telecomgear
telecomgear
timbreck
  • Question
Connecting avaya ip office 500 v2 to a valcom page system 1
2
Replies
26
Views
1K
timbreck
timbreck
TN94z
  • Locked
  • Question
IP Office/Voicemail Pro Emergency close situation
Replies
14
Views
315
IamaSherpa
IamaSherpa
CPM86
  • Locked
  • Question
IP 500 bri 4 and 8 Trunk card for old ISDN phone use?
Replies
4
Views
150
derfloh
derfloh

Part and Inventory Search

Sponsor

Back
Top