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

IPoffice Change IP address and VoiceMail

Status
Not open for further replies.

pgordemer

IS-IT--Management
Dec 10, 2002
80
US
We have an older IP 406 in our Main office and 3 IPOffice units running 3.2. This has been running OK for quite awhile. (save the occasional VoiceMail reboots for sanity).

We changed the IP address of 2 of the units, and updated the VOIP IP address in all the units. We are communicating correctly, SCN seems to be working fine, but for 1 office, if the call is not answered and it bounces back to Voicemail, you get bounced to your own voicemail. Its as if the VoiceMail server isn't seeing the new Ipoffice unit at the IP. I can ping all the units and they can all see each other.

Any thoughts on where to look.
 
Re-create the VoIP Line to that office, on both ends of the link, dont forget to set the SCN Line for the VM after you recreate the link.

Mr IPO

ACA - Avaya Certified Associate
ACS - Avaya Certified Specialist
ACI - Avaya Certified Instructor
Components-t0098.jpg

 
Do I need to recreate this on all 4 IPoffice units, the same misdirected Voicemail happens from any of the other offices.

I will start with at least recreating the IP connect from the effected office to the Voice Mail location - though the actual calls work fine.
 
Still no luck, I recreated the IP line to that office in every unit. We voice communicate perfectly to that office, you can't just leave them a voice mail, you get your own. the other thing I notice is when you dial the extension for that office, you don't see the name, just the extension. Someone that office isn't finding the VoiceMail server.

I am positive, it is setup as central voicemail, with the IP Line # as location.
 
Are you able to ping the problem IP office from the VM Server, Pehaps the default route on the Server does not know how to route to the new addressing?

Let me know

Mr IPO

ACA - Avaya Certified Associate
ACS - Avaya Certified Specialist
ACI - Avaya Certified Instructor
Components-t0098.jpg

 
You can ping everywhere, the VM server and the IP406 host are in the same segment. You can talk from every office to this office, and visa versa. If you even try to check your voice mail, you get nothing.

If I create a new extension, Voicemail folders dont get created. I have confirmed that Voicemail is set to Line/Central with the Line ID of the VOIP IP line.

Each IPOFFICE has a default route going to the cisco router rather than individual routes in the IPOFFICE.
 
Anyone - we are still stuck and our Vendor is clueless.

Its not a routing issue, since my short code dialing is working. This is a SCN issue I am sure since I am not seeing the extension name for this problem office. If I create a new extension, a VMailbox is not created.

IP406 - HQ
IPoffice - North
IPOffice - BB (Problem office)
IP403 - CS

HQ is the master. All other locations are VPN from HQ. All offices can talk to any extension via IPLine. All offices except BB can check their voicemail. The IPLine for HQ to BB has been deleted and recreated twice. But again, We can talk between that location.

The voicemail server can ping every office including the problem BB office. From the BB office I can ping the mail server and any other office phone unit.

These are stuck on version 3.1 (Would love to upgrade to 3.2, but I have been told there isn't enough memory to do that).

 
What kind of system is it ?
There is no system that is limited to 3.1
It is 3.2 wich is the highest you can go (like the 403)


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
I agree it should be at least up to 3.2, but this vendor claims it can't be done. I can't argue at this point with them as the last time I tried a upgrade I bricked a unit.

I can't wait for this contract with this vendor to expire so I can get some real help, but for now.... **sigh**.

 
What is the system ?
403 Small or 406v1 ?

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
The part that is driving me nuts is this has worked fine for almost 2 years.

We have been IP renumbering each of the offices and just making the change ip IP address and Voip as we renumber each office. All was fine until we got to this BB office.

The only thing that I am starting to belive is I have been told it easy to corrupt the configuration of an IPoffice, and I am starting to believe that is the problem as this office config gets changed often.

I can't blank it out as I have to get to it from remote.
 
It is possible
Let someone put down a pc directly connected to the ipo
Export the config with that pc
Then go to "file" and "advanced" and ërase configuration"
After that it will be default (maybe the ipadres too,not sure)
Then import the config back in


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
406 v1 have more problems going to 3.2 than 403s do. They both can stall and appear to be bricks. You can still recover those via DTE and pointing to the original version of firmware.

IMO the best way to upgrade v1s and 403s to any version of 3.2 is to default the unit, upgrade firmware via DTE then send the config back.
 
No need to default it first
When you have a pc local then also connect the DTE

Then do an AT -> at-debug -> upgrade

This will be an offline upgrade
So you need to open the config first with manager for a bootp entry !!!

This way you can do it completly remote




ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Remote upgrade... You are a brave Indian Keemosabi. Not so bad with v2s and 500's I suppose.
 
Remote upgrade by vpn or isdn (more then an hour drive) is no go
But when you can take over a pc that is directly connected to the ipo with lan and serial cable there is no problem

But indeed it is less fun on a ip500 or 406v2 :)


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Well still no further along on this. Deleted IP line and recreated on every unit in every office 2 and from the BB location. We can shortcut dial to and from this office so routing and communications is working. Voicemail is set to Line/Central and the Line # of the HQ Voicemail system, but still no go.

If I try to leave them a voicemail, I get redirected to my own voice mail. If they try to check they voice mail, they get the prompts, but is immedately says invalud password. If I create a new extension, VMbox doesn't get created.

This has to be an SCN issue as I am not seeing the diaply of the extension data until they actually pickup.
 
are you sure that port 50791 is open on the BB site ?
Voicemail uses a different port then the rest


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
All ports are open, this is a hardware VPN (Sonicwall 3600 to Sonicwall 2040 Enhanced OS)and was not changed. Only the IP number range in the VPN was changed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top