From 293a65c9c05d4d02ab0746734e979320fabbe1c9 Mon Sep 17 00:00:00 2001
From: kapil <kgupta@sangoma.com>
Date: Wed, 6 Jun 2012 14:45:39 +0530
Subject: [PATCH] updating final xml config file

---
 .../endpoints/mod_megaco/conf/megaco.conf.xml | 65 +++++++------------
 1 file changed, 23 insertions(+), 42 deletions(-)

diff --git a/src/mod/endpoints/mod_megaco/conf/megaco.conf.xml b/src/mod/endpoints/mod_megaco/conf/megaco.conf.xml
index e21ab3a074..91f8f0cc63 100644
--- a/src/mod/endpoints/mod_megaco/conf/megaco.conf.xml
+++ b/src/mod/endpoints/mod_megaco/conf/megaco.conf.xml
@@ -1,47 +1,28 @@
 <configuration name="megaco.conf" description="Megaco Controllee">
 
   	<!--Each instances of MG will have each mg profile  -->
-	<sng_mg_interfaces>
-		   <sng_mg_interface name="default">
-			   <param name="id" value="1"/>                			<!-- /* equivalent to SSAP ID of MEGACO layer */-->
-			   <param name="protocol" value="MEGACO"/>         		<!-- /* Protocol Type , Supported values are MEGACO/MGCP */ -->
-			   <param name="version" value="3"/>         			<!-- /* Protocol Version , Supported values for MEGACO are 1/2/3 */ -->
-			   <param name="transportProfileId" value="1"/>   		<!-- /* Link to transport layer configuration --> 
-			   <param name="localIp" value="192.168.1.101"/>  		<!-- /* Local node IP */ -->
-			   <param name="port"     value="2944" />	    		<!-- /* Port */ -->
-			   <param name="myDomainName" value="mg.sangoma.com" />   	<!--/* Local domain name */ -->
-			   <param name="mid" value="<lab.sangoma.com>"/>        		 <!-- /* Message Identifier (MID) of MEGACO message  */ -->
-		           <param name="peerId" value="1" />  	    		 	<!--/* MGC Peer Configuration profile ID */-->
-			   <!--/*We can define multiple peer_ids depends on number of MGC per MG.
-		  	   MGC Priority          - peer order can defines the priority or we can priority attribute in peer_id element..Not needed now..we can think later
-		 	   Primart/Secondary MGC - we can think later in future when we need this functionality..as of now not requied. */
-			  -->
-                    </sng_mg_interface>
+   <mg_profiles>
+	   <mg_profile name="default">
+		<param name="protocol" value="MEGACO"/>  			<!-- /* Protocol Type , Supported values are MEGACO/MGCP */ --> 
+		<param name="version" value="3"/>         			<!-- /* Protocol Version , Supported values for MEGACO are 1/2/3 */ -->
+		<param name="local-ip"  value="192.168.1.103"/> 		<!-- /* Local node IP */ --> 
+		<param name="port"      value="2944" /> 		 	<!-- /* Port */ -->
+		<param name="domain-name" value="lab.sangoma.com" />   		<!-- /* Local domain name */ -->
+		<param name="message-identifier" value="<mg.sangoma.com>" />   	<!-- /* Message Identifier (MID) of MEGACO message  */ -->
+		<peers>								<!-- /* List of Peers associated with this MG Profile */ -->
+			<param name="peer"  value = "peer-1" /> 		<!-- /* link to peer configuration block */ -->
+		</peers>
+	    </mg_profile>
+    </mg_profiles>
 
-    </sng_mg_interfaces>
+    <mg_peers>
+         <mg_peer name="peer-1">
+        	<param name="ip"  value="192.168.1.102"/> 			<!-- /* Peer node IP */ -->
+	        <param name="port" value="2944"/> 				<!-- /* peer port */ -->
+        	<param name="encoding-scheme" value="TEXT"/>         		<!-- /* H.248 Encoding scheme TEXT/BINARY */ --> 
+	        <param name="transport-type" value="UDP"/>          		<!-- /* TCP/UDP/SCTP */ -->
+        	<param name="message-identifier" value="<remote1.mgc.com>" />     <!-- /* Message Identifier (MID) of remote MGC MEGACO message  */ -->
+        </mg_peer>
 
-    <!--/*transport profiles which can be TCP, UDP or SCTP */-->
-    <sng_transport_interfaces>
- 
-    	 <!--/* for TUCL we dont need any layer specific config parameters */ -->
-		     <sng_transport_interface name="TPT-1">
-			  <param name="id" value="1" />   		  	 <!-- /* transport profile id    */ -->
-		    	  <param name="transportType" value="UDP"/>   	 	 <!-- /* transport profile type values could be UDP/TCP/SCTP */ -->
-                    </sng_transport_interface>
-
-    </sng_transport_interfaces>
-
-
-    <sng_mg_peer_interfaces>			 				<!--/* Supported number of peers */ -->
-
-   		   <sng_mg_peer_interface name="MG_PEER1">
-			   <param name="id" value="1"/>         		<!-- /* Peer profile ID */-->
-			   <param name="ip" value="192.168.1.100"/>  		<!-- /* Peer node IP */ -->
-			   <param name="port" value="2944"/>   			<!--/* peer port */ -->
-			   <param name="encodingScheme" value="TEXT"/>  	<!--/* H.248 Encoding scheme TEXT/BINARY */ -->
-			    <param name="mid" value="<remote.mgc.com>" />    	<!-- /* Message Identifier (MID) of remote MGC MEGACO message  */-->
-		   </sng_mg_peer_interface>
-
-    </sng_mg_peer_interfaces>
-
-</configuration>
+ </mg_peers>
+ </configuration>