It really depends on the type of firewall and the policies associated with
it. However, in general, whenever you deal with protocols that include
information about one stream in another stream (e.g. RTP in H.245 or SDP,
or H.245 in H.225.0) you have a need to peak inside the stream (and thereby
be able to decode it) to determine what to let through and not.
Regards
Flemming Andreasen
Matt Holdrege <matt(a)ASCEND.COM> on 03/31/99 10:57:14 AM
Please respond to Mailing list for parties associated with ITU-T Study
Group 16 <ITU-SG16(a)mailbag.cps.intel.com>
To: ITU-SG16(a)mailbag.cps.intel.com
cc: (bcc: Flemming Andreasen/Bellcore)
Subject: Re: H.320 gateways a MEGACO / ITU
Such as?
In it's simplest form, a firewall is simply a filter. You can add on IPsec
functionality and other things, but that wouldn't affect a stream of PER
data.
At 10:50 AM 3/31/99 -0500, Melinda Shore wrote:
>Well, it depends. You've still got the problem of picking up
>any dynamically-assigned/allocated information, NAT or no.
>
>Melinda
>
>At 07:31 AM 3/31/99 -0800, Matt Holdrege wrote:
>>To be more accurate, PER may not work fine through a NAT function. If
your
>>firewall doesn't do NAT, then PER should have no problems.
>
>Melinda Shore
>Member of the Scientific Staff
>Nokia IP Telephony
>127 West State Street
>Ithaca, New York 14850
>+1 607 273 0724 x81 (office)
>+1 607 275 3610 (fax)
>+1 607 280 0010 (mobile)
>shore(a)ithaca-viennasys.com
>
