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

["Schwarz, Albrecht (Albrecht)" <[e-mail]>]

[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]<mailto:[e-mail]>>
Date: Wed, Jul 14, 2010 at 10:52 AM
Subject: ReservedGroup Usage for IPV4-IPv6 calls
To: [e-mail]<mailto:[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