On 1/27/11 3:34 PM, Tony Graziano wrote:
When an invite comes from the provider and says the address and port
"123.456.789.10:5080" and it needs to say instead
"123.456.789.10:5060", its not the PACKET that needs to be translated
or the address, its what is INSIDE the header, not the actual packet
destination.
Right, layer 7.
This means something has to actually take the header message and
rewrite it with the correct information. A simple PAT or NAT in a
firewall is not going to be able to do this in any event.
Right, PAT or NAT can only do layer 4.
The fact that it worked meant that something else is very wrong. maybe
as Tony said, the firmware was doing something (by accident) that it
should not. and in fact, it didn't do the right thing all the time
(when trying to support G.729 in fact)
still say a perl daemon or a couple copies of netcat could probally do
it. also, using FS as a proxy/ lightweight gateway might do it.
and/or, sipx can allow you to change the ports, and let the trunks
listen on 5060 and sip_srv use port 5080.
(which it can't today)
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
>*| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
