<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
Morning All,<br>
<br>
We are working with a Net VX SBC that has multiple customers
downstream and a single carrier upstream, to all intents and
purposes<span style="color: rgb(0, 0, 0); font-family: Arial;
font-size: 16px; font-style: normal; font-variant: normal;
font-weight: bold; letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform: none; white-space:
normal; widows: 2; word-spacing: 0px; background-color: rgb(255,
255, 255); display: inline ! important; float: none;"><small></small>
</span>the downstream customers have services directly with the
upstream carrier. The upstream carrier allocates a set of
credentials which are ACL'ed to a specific point-to-point subnet for
each service. In our scenario we have a set of credentials and
corresponding interconnect for each downstream customer. The carrier
provides a single set of signaling and media addresses across all
services..<br>
<br>
To the best of our knowledge, the SBC only supports a single routing
instance, hence when traffic destined for the upstream provider is
sent out, it can only follow one route. To get around this, and
ensure that traffic goes out over the correct point-to-point
interface, we intended to impliment a policy-based-route, assuming
that the SBC would source traffic from the IP of the SIP instance
regardless of what interface the traffic left the SBC on, this
appears to be incorrect however and the traffic is always sourced
from the IP on the interface of the default route. Interestingly at
a SIP layer everything looks OK.<br>
<br>
To further complicate matters the SBC is managed by a third party.<br>
<br>
Has anyone done anything similar in the past, with Net equipment or
otherwise? <br>
<br>
Any feedback much appreciated.<br>
<br>
Cheers<br>
Nick.<br>
<br>
</body>
</html>