can't ping ipoffice over wan

[jeepguy267]

Main Location has an IP Office small office behind a cisco pix. Remote location has a linksys BEFVP41 to establish a vpn tunnel. I am at the remote location and the tunnel works and I am able access network resources. I can ping the server with the manager and license apps, but I am not able to ping the IP Office. I am using remote desktop to the server to Monitor the IP Office and see the request come in. I have my routes built and am wondering if I need to have some sort of permissions built using RemoteManager or if the IP office firewall is at play? (does the firewall need to be licensed to be active or is a "green feature")

thanks

 

[RePetE815]

You indicate you have your routes correct. Could you share your routes as they are setup on the IP Office? This might help shed some light.

Confirm you have the IP Office SO setup with a default gateway which points to the PIX or a router with knowledge of how to get back to the remote location (via PIX). This would be setup under the IP Route tab under Manager. Should appear as follows:

IP Address: blank
IP Mask: blank
Gateway: internal LAN IP of PIX or backbone router
Destination: LAN1

 

[jeepguy267]

Thanks for the post. I removed all "extra" routes and have it back at just the default gateway (like what you described above) and I am back where I can comunicate with the IP Office over the WAN.

However, I am trying to get a 4620 to come up and am having a variety of results. I have not been able to consistently replicate each of the little errors, but have found that occationally the system will add a route for "RemoteManager" after the 4620 tries to comunicate with the system. This route has my remote ip scheme with no gateway and the RemoteManager as the destination. With this route in place I cannot ping and am back to where I was with the first post. So the question becomes why is the IPoffice adding this route? and what do I need to get my 4620 going.

I am using a fixed IP on the local lan for the 4620, IP office (at main branch) as gateway, local Linksys device as router and remote server address for file server. It does pull the 46xx file, but hangs at different places with the many reboots.

any thoughts?

 

[RePetE815]

Have you tried changing the route for RemoteManager to something different than your remote subnet address (e.g. 10.0.99.0/24)?

We too have 4620 IP phones traversing site-to-site VPN connections to a main location. While I can't attest to the matter of the route reappearing after deletion (I've never had a need to delete it) I can hopefully shed some light on my config here in the hopes that it proves helpful given your dilemma.

I would recommend having only two (2) routes (assuming we're just talking local and remote LAN connected via VPN). This would include the default as well as the apparent system default of RemoteManager WITH a different IP route specified (mine lists 192.168.99.0/24 which is different than my remote IP subnet of 172.x.x.x/24)

Our 4620 IP Phones have the following "manual" settings:

IP: static IP common to remote LAN subnet (i.e. 192.168.99.101)
CallSv: IP Office Unit IP
CallSvPort: 1719
Router: remote LAN default gateway (internal LAN IP of LInksys)
Mask: remote LAN mask
FileSv: Local LAN Manager Server
802.1Q: auto
VLAN ID: 0

Start logging on the Manager server and see if the 4620 is able to establish a connection and download the appropriate .bin file, etc.

 

[IPGuru]

The IPO will always create a route 192.168.99.0 to RemoteManager if it is present in the user list.

Solutions:

1) do not use 192.168.99.0 on your internal network
2) Rename the usere RemoteManager

 

[jeepguy267]

Thanks Guru,

I thought it was me. My remote location LAN happens to be 192.168.99.0 - I renamed default user RemoteManager to RemoteMgr

my 4620 is hanging at the "discovering..." phase. I had this set working directly plugged into a bench system as ext 222. In the remote location the system does create a new extension 222, so some things are working.

 

[IPGuru]

I would sugest defaulting the settings of the 4620 & starting again.

<Hold> *73738* - or for those of you with letters on the keypad <Hold> *RESET*

 

[jeepguy267]

guru,

I have some consistency at this point, but I don't feel comfortable posting straight from my sysmonitor until I know what I am showing. I know it goes against the nature of the forum, but would you be willing to go off line for a bit? I can then post helpful findings back here for others to benefit

 

[jeepguy267]

this is the info from sysmonitor. I see the setting.scr file get uploaded, then the phone just hangs.

3424877mS PRN: Recv: SwitchInfoRequest
3424917mS PRN: WARNING:
3424917mS PRN: TPKT Recv: Invalid header
3424918mS PRN:
3424918mS PRN: Should delete1
3425243mS PRN: Recv: GatekeeperRequest
3425312mS RES: Fri 28/5/2004 13:53:25 FreeMem=5766756(11) CMMsg=4 (5) Buff=100 653 485 1458
3425445mS PRN: Recv: RegistrationRequest reply addr c0a86323
3425446mS PRN: RasServer::OnRRQ --- CallSigProtocol is H323AnnexL_P. Go for IP4600 R2
3425446mS PRN: Reject unforced-login --- Existing: ffe07000; force-login: 0
3425483mS PRN: Recv: SwitchInfoRequest
3427786mS PRN: Recv: SwitchInfoRequest
3430124mS PRN: Recv: SwitchInfoRequest
3430300mS RES: Fri 28/5/2004 13:53:30 FreeMem=5768348(12) CMMsg=4 (5) Buff=100 653 485 1458
3603958mS PRN: GK: Removing endpoint system1_40b74454215a219e
3603959mS CMExtnRx: v=231, p1=0
CMPhoneStatus
Line: type=NoLine 0 Call: lid=254 id=0 in=0
Cause=18, NoUserResponding
3604320mS RES: Fri 28/5/2004 13:56:29 FreeMem=5772080(12) CMMsg=4 (5) Buff=100 653 485 1458

 

[mikeduncan]

Make sure you disable h323 fixups on the PIX.

see:

http://www.tek-tips.com/viewthread.cfm?SQID=842999&SPID=940&newpid=940&page=1