MEGACO version in ServiceChange Reply

--===============4855619116330119061==
Content-Type: multipart/alternative; boundary=f46d04389095a16ce804c7dd99b9

--f46d04389095a16ce804c7dd99b9
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Assume MG sends a ServiceChange encoded as MEGACO/1 with VERSION=3

MGC supports offered version, how does it encode the response; as MEGACO/1
or MEGACO/3? I see the example in ITU H248.1 (09/2005) Appendix I showing a
response of MEGACO/1 but I was unable to find this discussed anywhere else
in the specification.

Thank you

Chaim Geretz

--f46d04389095a16ce804c7dd99b9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi,</div><div><br></div><div>Assume MG sends a ServiceChange encoded a=
s MEGACO/1 with VERSION=3D3</div><div><br></div><div>MGC supports offered v=
ersion, how does it encode the response; as MEGACO/1 or MEGACO/3? I see the=
 example in ITU H248.1 (09/2005) Appendix I showing a response of MEGACO/1 =
but I was unable to find this discussed anywhere else in the specification.=
</div>

<div><br></div><div>Thank you</div><div><br></div><div>Chaim Geretz</div><d=
iv><br></div><div><br></div><div><br></div>

--f46d04389095a16ce804c7dd99b9--

--===============4855619116330119061==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco

--===============4855619116330119061==--