Re: [Megaco] Fwd: ReservedGroup Usage for IPV4-IPv6 calls

[raj kumaradass <[e-mail]>]

MG1 and MGC supports dual stack.  In such cases, a underspecified SDP
template alike below will be included with RG set to required in the Add
msg:

M{
O{MO=RC,RV=NOTREQ,RG=REQUIRED},
L{
v=0
c=IN IP6 $
t=0 0
m=audio $ RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:10
v=0
c=IN IP4 $
t=0 0
m=audio $ RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:10
}

Is the above approach valid? And also would like to know if there are any
guidelines/standards available upon the usage of reservedGroup, as RFC3525
does elaborates little on this.

thanks,
...Raj

On Mon, Aug 9, 2010 at 5:14 PM, Schwarz, Albrecht (Albrecht) <
[e-mail]> wrote:

>  [MG1 supports only IPv6, right? Or supports MG1 dual-stack?]
>
> There are multiple call & gateway control options from perspective of the
> MG1-associated MGC:
>
> 1st Clarify IP version first end-to-end on call control level
>     Implies SDP Offer/Answer in case of SIP.
>     The MGC may use "a=ccap" (draft-ietf-mmusic-sdp-misc-cap) and
> potential configurations.
>
> 2nd Parallel establishment of IP transport connection in bearer plane.
> If MG1 supports only IPv6, then just exact specification
> If MG1 supports dual-stack, then two local destination IP transport
> endpoints may be reserved ... (with preference on IPV6).
>
> Thus, multiple options, nothing normative from my understanding.
>
>
>  ------------------------------
> *From:* [e-mail] [mailto:[e-mail]] *On
> Behalf Of *raj kumaradass
> *Sent:* Montag, 9. August 2010 12:40
> *To:* [e-mail]
> *Subject:* [Megaco] Fwd: ReservedGroup Usage for IPV4-IPv6 calls
>
> Resending the email.
>
>
> ---------- Forwarded message ----------
> From: raj kumaradass <[e-mail]>
> Date: Wed, Jul 14, 2010 at 10:52 AM
> Subject: ReservedGroup Usage for IPV4-IPv6 calls
> To: [e-mail]
>
>
> Greetings,
>
>
> Would like to know if the below handling of reservedGroup&underspecified
> SDP are valid:
>
> Originating Side MG1(IPV6) -- MGC (supports both IPv4/IPv6) --Terminating
> MG2 (IP details Not Yet known)
>
> When there's notification for offhook msg reported from the MG 1, the next
> transaction which consists of AddTermination to context, Apply dialtoneSG to
> physical term, requset on/flashhook from phy.term and add eph. termination
> ctxt.  Along with this, when there's a underspecified SDP to be sent in the
> Local SDP, it's mandatory to set the reserveredGroup flag to ON in LCO and
> include underspecified sessiondescriptors for IPV4 & IPV6, since the
> terminating side support is not known at this point.
>
> Appreciate your inputs.
>
> thanks,
> ...Raj
>
>
>