Hi Martin,

You should check the first INVITE for internal domain and rewrite the R-URI. Subsequent request should have the "changed R-URI", even for loose route. That's what I understand. Correct me if I'm wrong.

Zeus

-----Original Message-----

Hi Zeus,

no, this is not working. The Request-URI is not local for Loose Routing requests, it is the URI of the last point in the routing chain and thus remote. I need to validate the TO-Header field, not the Request-URI.

Regards, Martin

...

-----Original Message----- From: Zeus Ng [mailto:zeus.ng@isquare.com.au] Sent: Tuesday, September 07, 2004 4:03 PM To: 'Martin Koenig' Cc: serusers@lists.iptel.org Subject: RE: [Serusers] Domain and To header fields

Try is_uri_host_local().

Zeus

...

-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Martin Koenig Sent: Tuesday, 7 September 2004 11:33 PM To: serusers@lists.iptel.org Subject: [Serusers] Domain and To header fields

Hi List,

I have a multi domain ser setup with the domain module operating, and I need to check whether the TO header field contains a local domain or not.

Can this be done with is_domain_local()? If yes how?

Or do i need to write a new function based on is_from_local() to achieve such a goal.

The Problem is that there is no possiblity to distinguish between our user calling 012345@iptel.org (Remote SIP desination) or 012345@domain.com (PSTN target) after (!) the initial INVITE, especially with loose routing. This is important because Request-URIs to the PSTN have to be transformed (add f.e. +49), but requests to other sip destinations have to not

be touched.

...

...

Thanks for your input,

regards, Martin

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Hi all,

At 03:33 PM 9/7/2004, Martin Koenig wrote:

...

Hi List,

I have a multi domain ser setup with the domain module operating, and I need to check whether the TO header field contains a local domain or not.

I don't know if there is any real meaningful use for it, since To is informative only. In scenarios with multidomain forwarding, it has no affinity to the domain you serve. If you nevertheless think it helps you, then rewriting is_from_local is I guess the fastest way forward for you.

A call to the PSTN will have To: 012345@localdomain

A call to IPTEL will have To: 012345@remotedomain

That is the main difference. As defined for loose routing, the Request-URI of lets say an ACK will be 012345@finaldestination, so this is a remote domain in all cases and cannot be checked. PSTN-calls need to be processed because we support multiple prefixes based on the user's group.

So yes, we will try to go with the rewrite of is_from_local()

...

Can this be done with is_domain_local()? If yes how?

Or do i need to write a new function based on is_from_local() to achieve such a goal.

The Problem is that there is no possiblity to distinguish between our user calling 012345@iptel.org (Remote SIP desination) or 012345@domain.com (PSTN target) after (!) the initial INVITE, especially with loose routing. This is important because Request-URIs to the PSTN have to be transformed (add f.e. +49), but requests to other sip destinations have to not be touched.

As said, it is fairly diffucult to recognize relationship to domain for subsequent requests unless the initial domain is piggybacked someway.

...

Thanks for your input,

regards, Martin

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

-- Jiri Kuthan http://iptel.org/~jiri/