Remote H.323 Extension Problem

[Stengrad]

I have a single 9608 that I am having issues with connecting remotely. On this 9.0.7 system, I have successfully set up and tested 2 remote IP phones already. These are not currently registered to the system. I am trying now to get a third to register, but it keeps going to a screen which shows "Registering", and has "Reset" on the bottom left soft key. After a time it goes to another screen which shows Press <> for list", and has "251" on the right side buttons. It then almost immediately goes back to the "Register" screen. I understand that only 2 remote phones will work with essential, but none are currently registered, and the problem phone is the only one set to "enable remote worker" on the user tab. Monitor shows the following:

12:41:58 947888663mS H323Evt: Recv GRQ from 46a99657
12:41:58 947888664mS H323Evt: e_H225_AliasAddress_dialedDigits alias
12:41:58 947888664mS H323Evt: found number <403>



Any ideas?

 

[amriddle01]

So you need to find what's different, the system programming is correct as it already works, the port forwarding is correct for the same reason, what has changed is the users loacation and broadband provider/router, that's where the issue will be, some ISP's routers just don't work/allow it

 

[Stengrad]

Sorry for the delay in replying. I was waiting for the phones 2 "working" phones to arrive at the site. They have, and are having the same issue. This would point to something at the main location that has changed. I can see the following in monitor trace:

14:50:26 1474042014mS RasRx: v=IFace=LAN1, Src=72.83.141.92:49304, Dst=192.168.45.2:1719 peb=0
RasMessage = gatekeeperRequest
14:50:26 1474042015mS H323Evt: Recv GRQ from 48538d5c
14:50:26 1474042015mS H323Evt: e_H225_AliasAddress_dialedDigits alias
14:50:26 1474042015mS H323Evt: found number <201>
14:50:26 1474042015mS RasTx: v=Src=192.168.45.2:1719, Dst=72.83.141.92:49304 peb=0
RasMessage = gatekeeperConfirm


Looks like they are trying to talk, but I don't know enough to determine exactly where the communication breakdown might be.

 

[amriddle01]

Have you ever had remote phines working from that location?
Have you took the 3rd handset that originally didn't work to the location(s) where the 2 handsets did work?

 

[Stengrad]

The "working" phones are the only ones at the remote site, and are not working now, (they have not worked at that site at all).

The 3rd phone was tested at the original site (my office) where the 2 working phones were originally set up and tested ok.

Senior Field Technician
Hampton Roads Communication Technologies

Http://hrct.net

 

[Stengrad]

Figured it out, but I don't know how it worked when I set the 2 phones up at my office. I had the customer's old Public IP address set in the network topology tab. I had a remote IP phone set up a couple of years ago, but that site went to a vpn connection, so I changed that phone to accommodate the vpn connection.

Recently, the customer moved, and their public IP changed. I had forgotten about that setting in the network topology tab. As soon as I changed the public IP address to the correct one, and rebooted, the phones registered!

Senior Field Technician
Hampton Roads Communication Technologies

Http://hrct.net