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!

Help with Avaya 5610 and remote IPO 3.0

Status
Not open for further replies.

BURLYMAN

IS-IT--Management
Aug 19, 2002
124
US
I have a customer that has a business office running IP Small Office 3.0. This customer has a home office that has a very solid VPN connected to the office. I am able to remote desktop back and forth, map network drives, etc.. etc.. There are no restrictions on this VPN at all (i.e. firewall rules, etc…) This VPN is router to router configuration so both networks can access each other. I have iPhone on his computer and it works perfectly!!!! It can communicate with the IPO with no problems and make/receive calls. My huge issue is a 5610 phone in his home office. For some reason I cannot for the life of me get this thing to work! I have the 5610 configured with correct settings (IP address is on home LAN, Gateway is on home LAN, CallSRV is the IPO in the business office, and the FileSRV is the VoiceMail Pro server in the business office). The interesting thing is that the 5610 pulls the .SCR and 46xxxsettings.txt files from the remote business office with absolutely no issues (so I know that routing is working perfectly). Then the telephone asks to register with the IPO which works great (after I register an extension the extension is applied within the IPO – and I have tried this numerous times with numerous extensions. When I open the configuration of the IPO the extension shows up just as it should). But then……….the 5610 will hang for a moment and then display “Extension in use # to register”. Even if I manually create the extension, etc. etc.. it acts the same way. The only troubleshooting information that I have is from the monitor which consistently and repeatedly says the same information (the extension in this log is 199):



----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Line: type=NoLine 0 Call: lid=0 id=-1 in=0

Cause=18, No user responding/No response from remote device

8220mS PRN: GK: Adding new endpoint RCISIPO1_4287875bffffe225

8220mS PRN: RRQ from 0a000032 - User 199, 0a000032 allowed, bchan 0.0, EI RCISIPO1_4287875bffffe225

8220mS PRN: Using IP_Phone 2.130

17421mS RES: Sun 15/5/2005 17:31:17 FreeMem=4338808(25) CMMsg=5 (6) Buff=100 589 498 1433 5 Links=10191 Elements=83

18282mS PRN: Recv: GatekeeperRequest 0a000032

18360mS PRN: Recv: RegistrationRequest 0a000032; Endpoints registered: 0; Endpoints in registration: 1

18361mS PRN: RRQ from 0a000032 - CallSigProtocol is H323AnnexL_P. Go for IP4600 R2

18362mS PRN: GK: Removing endpoint RCISIPO1_4287875bffffe225

18362mS CMExtnRx: v=199, p1=0

CMPhoneStatus

Line: type=NoLine 0 Call: lid=0 id=-1 in=0

Cause=18, No user responding/No response from remote device

18364mS PRN: GK: Adding new endpoint RCISIPO1_42878766ffffe226

18365mS PRN: RRQ from 0a000032 - User 199, 0a000032 allowed, bchan 0.0, EI RCISIPO1_42878766ffffe226

18365mS PRN: Using IP_Phone 2.130

28418mS RES: Sun 15/5/2005 17:31:29 FreeMem=4338792(25) CMMsg=5 (6) Buff=100 589 498 1433 5 Links=10191 Elements=83

28423mS PRN: Recv: GatekeeperRequest 0a000032

28512mS PRN: Recv: RegistrationRequest 0a000032; Endpoints registered: 0; Endpoints in registration: 1

28513mS PRN: RRQ from 0a000032 - CallSigProtocol is H323AnnexL_P. Go for IP4600 R2

28514mS PRN: GK: Removing endpoint RCISIPO1_42878766ffffe226

28514mS CMExtnRx: v=199, p1=0

CMPhoneStatus

Line: type=NoLine 0 Call: lid=0 id=-1 in=0

Cause=18, No user responding/No response from remote device

28516mS PRN: GK: Adding new endpoint RCISIPO1_42878772ffffe227

28517mS PRN: RRQ from 0a000032 - User 199, 0a000032 allowed, bchan 0.0, EI RCISIPO1_42878772ffffe227

28517mS PRN: Using IP_Phone 2.130

----------------------------------------------------------------------------------------------------------------------------------------------------------------------



This looked to me to be a routing problem because after the phone asks to register and the extension is created (from the log above) it says no user responding – so I thought that maybe the IPO did not know how to route back to the extension but as I said all other routing between computers work great. I have checked the IPO IP Routes and even re-created the default route to point to the router at the business office (0.0.0.0 MASK 0.0.0.0 USE 192.168.1.1). I am able to ping the IPO from the home office and I get replies fine. Might I be missing anything???

I have tested the IP phone on the local LAN where the IPO resides and the phone seems to work fine!

Thank you for your help in this matter!

 
I had just work through this simular problem and I have able to resolve the problem by making sure the 802.1Q was turned off since trunk was not being supported on the SOH side. I not sure if this will help, but it resolve my issue.
 
It was a bad phone? Did the phone work when it was connected to the Local LAN? My phone will work over the local LAN but refuses to work over WAN VPN
 
I was on the local LAN. I reset it no matter what I did it wouldn't come up. Replaced the phone with a new one it came up.

Your problem is not the phone if it comes up localy. You are looking at some sort of networking issue. What hardware/software are you using layerII/firewall?
 
Well - I'm fairly confident I have the answer to all of this. Apparently Linksys VPN routers do not support H323 V2 with Fragmented packets. According to Linksys none of their products support it and according to Avaya the routers must support it or it won't work. So - I guess I'm throwing in the towel on Linksys (I do know that the Netopia R910's work like a charm). It's really too bad because unless you have a home office that is willing to shell out a little more for a VPN router that can handle all types of VoIP traffic you are going to run into this kind of thing. Oh well - thats why the IT guys get paid the big bucks right?! Thank you for everyone's input.
 
Try sonicwall, I have it working and it's a cheap alternitive. Ask the IT guy if he's doing anything speacial to h323 traffic. if so tell him to stop!
 
I set up the VPN between the sites a while back wihtout knowing that IP Office was going to be used. According to Linksys, once the VPN is up there are no restrictions on traffic and you can't set parameters on the VPN interface so..... Also, according to Avaya Tier4 they have customers that are using Linksys VPN's with no problems they just wouldn't tell me what models (not sure why it would make a difference but I'm sure that it does because Linksys would rather just say "we don't support H323 V2 with fragemented packets" like I heard twice already)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top