[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] SIP Redirect Server and SIP Trunks
From:       Aniruddha Vaidya <anir123 () gmail ! com>
Date:       2009-06-29 18:02:57
Message-ID: 7759a74d0906291050w4f8988dby6c73d4d02d6dd1da () mail ! gmail ! com
[Download RAW message or body]

Hi All,

Thanks for your inputs. I looked through the RFC 4904. However I could
not find a suitable reference based on which a Redirect Server should
be able to insert trunking information in redirected address populated
in contact header.

According to the RFC, UAC and Proxies are able to insert trunk
information. According to section 6.3, a proxy that is aware of the
routing topology and supports rfc 4904, may insert destination trunk
group parameters in R-URI if none are present. On the similar lines,
can redirect server insert trunking information in contact header
field in 302 responses? So that when a new INVITE is formed for
redirected url, trunk group parameters are present in Request URI of
the new INVITE?

Can you please let me know if this is permitted?

Thanks,
Aniruddha

On 6/27/09, Victor Pascual Ávila <victor.pascual.avila@gmail.com> wrote:
> On Fri, Jun 26, 2009 at 10:06 PM, Aniruddha Vaidya<anir123@gmail.com>
> wrote:
>> Hello Everyone,
>>
>> I have a requirement wherein a Redirect server needs to populate
>> redirected address with SIP trunking information in contact header of
>> 302 response.
>>
>> One option that we are considering of is to use maddr parameter to
>> store SIP trunking information. Can you please let me if this is the
>> correct way to put trunking information in contact header or there is
>> any other mechanism of doing this?
>>
>> Thanks in Advance!
>> Aniruddha
>
> You might be interested in taking a look at RFC4904.
>
> Cheers,
> --
> Victor Pascual Ávila
>


[prev in list] [next in list] [prev in thread] [next in thread]