atcomsystems.ca/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems Remote Phone problem

I have nothing but problems with comcast and remote IP phones.

The behavior they don't like sounds normal.
have you got wireshark traces yet?

Yeah got the traces sent them to Samsung and they said what I already new that it's the firewall blocking the ports.
I'm not good with wireshark traces but I'm happy to share them.

There usually are ports that need to be opened (forwarded) on the firewall to allow audio & BLFs both ways. Every system is different, but your Samsung manual should have a list---or your Samsung support should be able to give those ports to you. On the system that we install, I have a list of ports that we forward (open). That usually takes care of it on the main end. On the far (remote ) end, you have to open up the ports on the Comcast router/firewall. Without both being done, you will have problems. Comcast does not do this for you.
It can be very frustrating for the first few times that you do these procedures. Hang in there.

It does not look like your port forwards are set up correctly for the remote IP phone.

6000 TCP and UDP should be forwarded to the processor. It looks like you only have UDP.

9000 and 9001 should not be port forwarded. Those are the ports that the phone will source from.

Also, you should not start your audio for the SVMI on an odd number. Odd number is for RTSP. Even number is for RTP.

Assuming the following:

MP20 = 10.16.149.3
OAS = 10.16.149.4
SVMI 20i = 10.16.149.5

TCP/UDP 6000 Port Forward to 10.16.149.3
UDP 30,000 - 30,031 Port Forward to 10.16.149.4
UDP 30,032 - 30,071 Port Forward to 10.16.149.5 (Assuming 20 ports of VM licensed)

Be sure to log into system and set your RTP start port to 30,032 for your SVMI and 30000 for your OAS card.

Remove the UDP 9000 and 9001 rule.

If you want remote access via DM to system:
TCP 5090-5091, 50021 should be pointed to 10.16.149.3

If you want remote acces to SVMI 20i
TCP 6001,6002, 21, 60024 should be forwarded to 10.16.149.5

Port 21 is a bit trickey because both the SVMI and OS use it for file transfer.
In DM, you can change this port for the OS when you create your connection. Change it to 50021
In your firewall, you would port-map it back to 21 before it gets to the OS.

Hope this helps.

Terrell
My Youtube Channel https://www.youtube.com/terrellboyer

I've had a customer with remote ip handsets in the Philippines, who were having intermittent speech issues.

I had a handset on my desk connected which worked flawlessly, even put 1 in another staff members house which worked ok.

Turns out SIP ALG can interfere with no sip calls, it must pickup the RTP stream and assume it's a sip call.

Check that there is no ALG enabled.

Hello

Finally Got to the bottom of this so I thought I would let you know!
We knew it was the firewall causing the issues but didn't know why, the problem was the outbound rules set in the firewall it was sending the wrong ports back instead of the normal RTP 30000 range it was sending back ports 35000 RTPS ports.
I need to confirm what the firewall guy did but I think it was just have one outbound rule for the OAS card and no outbound rule for the mp20 and svmi.

Thanks for your help and comment with this:)