29 Sep
2006
29 Sep
'06
7:32 a.m.
You should (must) use DNS entries for openser1 and openser2 and just
use t_relay* calls to forward calls from one to another...
Samuel.
2006/9/29, Mark Kent <mark(a)noc.mainstreet.net>et>:
It depends in your config file...if the Request passed the loose_route
you have to process it in your config file accordingly...
> (due to
misconfiguration of listen|alias parameters) and that's why it
That can't be it as the box functions normally in less complicated
scenarios. Besides, I just added what you suggested and it doesn't
make a difference :-)
And, what's the interaction between the "domain" module and how
openser internally recognizes messages intended for itself?
And things work in simpler scenarios.
Then your "complex" config file is doing inapropriate things....
Let me tell you what makes this more complicated:
When OPENSER-ONE gets a call that is meant for the pstn it
sends back a redirect to the client, redirecting to OPENSER-TWO.
Some clients do start communicating with OPENSER-TWO, but some don't.
They send the new R-URI, mentioning OPENSER-TWO, to OPENSER-ONE.
I want to handle those messages as easily as possible, so right at the
top of route[0] on OPENSER-ONE I have this:
# kludge, sender should have been redirected earlier,
# but just in case...
if (uri=~"@OPENSER-TWO.example.com|@192.0.2.2") {
log(1, "stateless relay TO pstn gw\n");
forward();
exit;
}
if ((src_ip==192.0.2.2) && (!is_uri_host_local()))
log(1, "stateless relay FROM pstn gw\n");
forward();
exit;
}
The first "if" is for stuff addressed to OPENSER-TWO, but sent to OPENSER-ONE.
The second one is for messages coming back the other way.
As I sit and think about this, I'm guessing that I can't get away with
just shuffling the packets back and forth. But I could do with a
explanation as to how silly this is.
Thanks,
-mark