sundance-communications.com/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems Sonichell with 7200

Here are the notes that the sonicwall tech wrote:

-SIP is getting completed but there is no reply for the RTP traffic from the server
-He mentioned that the phone provide is not responding because the port numbers are getting changed while the packets are getting forwarded
-The port numbers are getting changed for SIP as well as RTP, SIP is getting completed but no reply packets for RTP
-Configured one to one nat for the RTP server 192.168.1.11 with another public IP address
-Now the port number for the RTP traffic is not getting changed but still no reply from the Server
-The Connection Information in SIP Invite packet is still carrying 192.168.1.11.
-If SIP transformation is enabled packets starts to drop on the sonicwall (Invalid Register)
-Asked to change the same to the public IP address of the Sonicwall, still no success
-Still the capture shows public IP address in the connection info of SIP packet.
-Issue seems to be the presence of public IP address on connection info in SIP packet

Any of you have a system with a sonicwall (newer) we just purchased them to replace our Cisco routers.

But because we are using an OAS card (that has it's own private IP) along with the private IP of the phone system. For some reason if we try to use just one public IP address to our SIP provider - the ports get changed on the send/receive. So the sonicwall tech fixed that by saying everything from the OAS was one public IP and everything from the phone system was another public IP - this worked to stop the ports from flipping.

But now no audio.

And it appears that the packets to the SIP provider are coming over as private IP's instead of public.

These devices don't seem to play well with Samsung voip.
You will need to turn off the sip alg (also called helper) I have the cli command somewhere.

Though last time I tried I had to set the system as private only otherwise I would get 1 way speech on incoming calls but outgoing would work fine.

I am seeing that - and I am going to return the sonicwalls - sucks cause I bought 2 of them and 6 AP's.

You can turn that ALG off now from the GUI.

You got yours to work with Private Only - that is how I have them working now on my Cisco ASA.

The problem is I have the OAS card and the system - each having it's won IP - and that is where the sonicwalls are choking. Cause it changes ports when it is set like this.

Hmmm, maybe this is a new software issue with SonicWall. I have been able to configure a 7200 with a Sonicwall to work for SIP. The system even has deployed IP phones. There is only one IP that is being used for the entire system. Maybe the NAT rules aren't setup correctly. You need to make sure that with the Sonicwall that the rules are applied for both incoming and outgoing under NAT. That will definitely get you if not setup right.