Hi,
> I need policy based routing, but the packet receiving interface is st0. Now
> you can not apply filter on st0. so FBF is failed here
> Can any body suggest the resolution?
The good old trick of a loop link could do it.
You could use logical tunnel, or pair of spare physical port with a
ha
Hi Paul,
> During a peer migration from a Cisco 7600 over to Juniper MX480 we have run
> across a particular peer that we cannot re-establish:
> Jun 9 13:17:07 core1.toronto1 rpd[1301]: bgp_process_open:2625: NOTIFICATION
> sent to xxx.xxx.115.132 (External AS x): code 2 (Open Message Error)
Hi Michel,
> I do have following settings in my config that related to "flow", but I am
> not sure if something I still missing...
If you have not already tried, the command 'get flow' gives details of flow
configuration.
Some in particular:
set flow reverse-route clear-text prefer
set flow
Hi Ivan,
> it is all direct, the alcatel omni handles the SIP, and then hands off to the
> phones, which talk direct RTP
> But I still can't understand how the firewall would know how to NAT the
> incoming traffic, first to the SIP server and then to each handset
Have you read through t
rect handset to handset?
Do you actually talk SIP handset to handset, or just RTP handset to handset?
-Original Message-
From: Ivan c [mailto:ivann...@gmail.com]
Sent: Monday, 23 November 2009 16:25
To: Tony Frank; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] ScreenOS and VoIP and NAT
I
You don't like to look in alex library or PRIMUS before asking external?
For GGSN where it is running:
Show services ggsn status ## note the version against the GGSN Node
Controller / Session Controller
For GGSN where it is not fully running:
Show version detail
## Match the J
6 matches
Mail list logo