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!

1616 remote extn problems 1

Status
Not open for further replies.

mknutson42

IS-IT--Management
Apr 28, 2015
20
US
I am having issues getting a 1616 to connect to my system. It will sit on Discover x.x.x.x screen. I have noticed that the file server IP does not seem to want to save everytime I look at the setup. It reverts back to 0.0.0.0. I am running IPO 8.1 and already have 2 remote phones working. I can get it to work on my 9621G in my office flawlessly but not the 1616.

I have ran a packet capture and I see traffic running both ways. Have verified IP Route and can ping both ways.

I am running out of ideas. Any help would be appreciated.

Thanks!
 
Do you have proper licensing? I think the IP office allows 2 Remote phones before licensing is needed... I could be wrong

Been there, done that
 
I have IP Endpoints for licensing. Although it seems the I do have the proper licensing as I can get my 9621 phone to connect to the system in question with no problems.
 
I did a little digging on the Knowledgbase... Looks like the 1600's are not supported

• Supported Telephones
Currently, remote H.323 extension operation is only supported with 9600 Series phones already supported by the IP Office system.
• License Requirements
By default, only 4 users can be configured for remote H.323 extension usage. Additional users can be configured if those additional users are licensed and configured with either Teleworker or Power User user profiles.

Been there, done that
 
Just to add onto thephonemn, we use 1616 phones with Avaya IPO500v2 on h.323 but we're on release 9.0.

We required additional licensing to allow our 8 phones to work.
 
That's it. I give up. This forum has officialy been overtaken by wannabe's.

"Never fear billing a client for services rendered, or they will think your time is worthless"
 
IPOfficeGuru, glad you brought this up, the way I look at it is this, every time we help someone out for free yes free we potentially loose income as the customer has no need to hire a qualified business Partner. So even thou this is a great site for fellow techs to receive help it is also killing revenue sales for the rest of us.
 
@IPOfficeGuru and @joe2938

I have to agree with you in some respect. We are a Business partner and I have the AIPS Certification. Now I will admit that I am probably not on your level with IP Office. I just posted on here to see if anyone has run into this and had a quick easy fix. I am not looking for free support. Just wanted to check before I call Avaya. We all know how well their support can be. :(

Again, sorry if it came across as wanting free support from billable technicians. I am not looking for free support or someone to spend more than 5min on this question.

 
I have no problems with other techs or business partners, it's the everyday customers that come to this site looking for free support and most do not even put in a little time to do their own research, by helping them for free I wonder how much revenue we really loose in the end.
 
16xx phones work on R8.1 software.
I have a system with 8.1 (69) and they have 174 16xx phones.
 
rdoubrava, did you miss the part where he said they are remote extensions? Or maybe your customer ha 174 remote extension phones?

"Trying is the first step to failure..." - Homer
 
Thank you all for the responses. I believe I have figured it out. It has to do with NAT rules. Once I connect the phone directly to the modem it connects to the phone system right away. I am going to be sending this to our network team to configure the firewalls to allow traffic.

Again thanks for the responses.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top