24 Sep
2004
24 Sep
'04
2:08 p.m.
Keith,
If I'm not mistaken, the From and To form part of the request's dialog
'key' along with the callid. To cannot be changed. If you did change
To
in the Level3 direction, when the request comes back you would have to
replace the
original 'To' from the UAC. I think this is, in effect, a psuedo b2bua.
I agree with Jiri, the request uri is what is important. However, you
know what they say about the 1000 pound gorilla :-)
-g
On Sep 24, 2004, at 11:13 AM, TSS Support wrote:
From: "Jiri Kuthan" <jiri(a)iptel.org>
Greg Fausak
www.AddaBrand.com
(US) 469-546-1265
Then the provider is using VERY questionnable
policy and ought to
look only
at request-uri.
* is a B2BUA -- it does not rewrite, it generates everything on its
own.
I personally think B2BUA is in most cases very suboptimal technology.
Scalability is an example, even if it does not matter in baby-sized
setups.
B2BUa security model is questionnable too.
See, this is the problem. The provider is Level3. We are trying to use
their Enhanced Local service rather than provide all of the toll
calling over our trunks. They insist that there must be e.164
formatted addresses in all header fields: From, To, and Request-URI.
The first and last are easy. It seems the only solution to fix the
middle one is to add a B2BUA or go in and patch SER. We don't want to
add another point of failure, so it's likely we'll end up adding
t_relay_to_level3() or something like that.
-Keith, TSS
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers