Remote connection of an LG WIT-400H WiFi handset to an iPECS 1

[JoeNewton]

Hi

We are having a major problem with a WIT-400H connecting remotely, via SIP, to an iPECS-50B. We installed the system before Christmas, it is the first iPECS that we have put in, before this the only LG systems that I have worked on are ip-LDKs and the occasional GDK. The handset worked fine on site, using both the internal and then the public IP address (once the relevant ports had been unblocked). The customer then took the handset home, which is the reason why they bought the phone in the first place, and it won't work. I have tried everything I can think of - our supplier's tech support say that it must be a network issue, but the customer's IT support company say that they have done everything that we have asked. I have now had the phone sent back to us to rule out the customer's home equipment, and user error, and I am having the same problem. The phone will make and receive calls with no problems, and activate call forward and DND etc, but during the call, 90% of the time, there is no speech. I have had 2 way speech on 2 occasions (out of 30-40 test calls) and 1 way speech once; however most of the time it is either silence or just distored noises. The firewall on my router is off. At the customer's offices, according to their IT company, all of the following ports have been unblocked and forwarded to the iPECS:

5060 TCP & UDP
5588 UDP
6254 UDP
7000-7015 UDP
7100-7115 UDP
7300-7315 UDP
8002-8005 UDP

Please can somebody help me find a solution to this?

Thank you!

Joe Newton
CCENT, CompTIA A+

 

[SteveBUK]

Hi Joe,

I would ensure that the router at the main site does not have/use a SIP ALG..... I have found that this can interfear with the SIP.

Also ensure that in PGM 102/103 you have the Firewall IP Address (which is the main sites Fixed Public IP Address) and the Gateway/routers IP Address.

Can also check PGM 140/141/142 to ensure that the VoIP Mode is set Commom (ie SIP or H323)

Regards
Steve

 

[JoeNewton]

Hi Steve

Thank you for your reply. This issue has now been sorted; it turned out to be the routers denial of service protection blocking the ports, rather than the firewall. I would have thought the IT company would have done this at the same time as the firewall, knowing that it has that function, but apparently not. As soon as they turned it off it worked fine.

Thanks

Joe

Joe Newton
CCENT, CompTIA A+