Northbound interface:Configuration:H248 - Revision history

Sylvain Fontaine: /* h248_media_gateway_controllers */

2015-11-27T21:26:27Z

h248_media_gateway_controllers

← Older revision		Revision as of 17:26, 27 November 2015
Line 172:		Line 172:
	},		},
	"ip_address" : "",		"ip_address" : "",
	"name" : "~~new_1~~",		"name" : "",
	"port_to_send_for_text_encoding" : 2944,		"port_to_send_for_text_encoding" : 2944,
	"position" : 0		"position" : 0

2015-11-27T20:58:04Z

h248_tdm_terminations

← Older revision		Revision as of 16:58, 27 November 2015
Line 65:		Line 65:

	The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'. Changing '''term_name_prefix''' will result in changing the '''{ElementName}''' in the collection.<br/>		The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'. Changing '''term_name_prefix''' will result in changing the '''{ElementName}''' in the collection.<br/>
	The default '''"term_name_prefix"''' is built by prepending 'TRK_' ~~suffix~~ to the associated '''"line_service"''' trunk name.		The default '''"term_name_prefix"''' is built by prepending 'TRK_' to the associated '''"line_service"''' trunk name.

	So, if the line service 0 name would be LS_0, we would get the following:		So, if the line service 0 name would be LS_0, we would get the following:

2015-11-27T20:54:12Z

@@ Line 47: / Line 47: @@
      "position" : 1
+   }
 == Getting the default values ==

2015-11-27T20:41:20Z

h248_tdm_terminations

← Older revision		Revision as of 16:41, 27 November 2015
Line 162:		Line 162:
	}		}

	The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'. Changing '''term_name_prefix''' will result in changing the '''{ElementName}''' in the collection.		The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'. Changing '''term_name_prefix''' will result in changing the '''{ElementName}''' in the collection.<br/>
	The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the associated '''"line_service"''' trunk name.		The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the associated '''"line_service"''' trunk name.

2015-11-27T20:41:04Z

h248_tdm_terminations

← Older revision		Revision as of 16:41, 27 November 2015
Line 162:		Line 162:
	}		}

	The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/' ~~<br>~~		The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'. Changing '''term_name_prefix''' will result in changing the '''{ElementName}''' in the collection.
	The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the associated '''"line_service"''' trunk name.		The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the associated '''"line_service"''' trunk name.

2015-11-27T20:40:09Z

h248_tdm_terminations

← Older revision		Revision as of 16:40, 27 November 2015
Line 163:		Line 163:

	The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/' <br>		The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/' <br>
	The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the ~~{TrunkName}, which is the~~ "line_service" ~~value here~~.		The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the associated '''"line_service"''' trunk name.

2015-11-27T20:38:57Z

h248_tdm_terminations

← Older revision		Revision as of 16:38, 27 November 2015
Line 162:		Line 162:
	}		}

	The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'		The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/' <br>
			The default '''"term_name_prefix"''' is built by prepending 'TRK_' suffix to the {TrunkName}, which is the "line_service" value here.

2015-11-27T20:36:52Z

h248_tdm_terminations

← Older revision		Revision as of 16:36, 27 November 2015
Line 153:		Line 153:

	Anyhow, the h248_tdm_termination element structure is the following:		Anyhow, the h248_tdm_termination element structure is the following:
	"~~TRK_~~{~~TrunkName~~}" : {		"{ElementName}" : {
	"line_service" : "{TrunkName}",		"line_service" : "{TrunkName}",
	"suffix_start_number" : 0,		"suffix_start_number" : 0,
Line 161:		Line 161:
	"use_timeslot_number" : true		"use_timeslot_number" : true
	}		}

			The '''{ElementName}''' corresponds to the '''"term_name_prefix"''' without the trailing '/'

2015-11-27T20:34:50Z

h248_tdm_terminations

@@ Line 150: / Line 150: @@
 === h248_tdm_terminations ===
 New element can't be added into h248_tdm_terminations collection on ''/configurations/{CfgName}/h248_stacks/gateway_h248/h248_tdm_terminations'' URI, therefore getting default parameters using ''/new'' is not possible.
-Elements in ''h248_tdm_terminations'' collection are automatically added when linking '''NAPs''' to '''h248_gateway'''.
+Elements in ''h248_tdm_terminations'' collection are automatically added when linking '''NAPs''' to '''h248_gateway'''.  E1/T1 trunks owned by linked '''NAPs''' will be populated in the ''h248_tdm_terminations'' collection.
-Here '''NAP_TDM''' is linked to '''h248_gateway''', therefore E1/T1 trunks owned by that NAP will be populated in the ''h248_tdm_terminations'' collection.
+Anyhow, the h248_tdm_termination element structure is the following:

2015-11-27T20:11:29Z

h248_stack

← Older revision		Revision as of 16:11, 27 November 2015
Line 5:		Line 5:
	== Element Addition (POST) ==		== Element Addition (POST) ==
	=== h248_stack ===		=== h248_stack ===
	This example uses default values mostly. Some attributes are given specific values, depending on the needs. There is also required attributes, for which no defaults exist. Here and '''transport_protocol.ip_interface''' and '''transport_protocol.public_ip_address''' are by default empty, and must be set otherwise the ''POST'' will be refused. The attribute ''naps'' ~~will~~ also be required to complete the overall configuration ,but can be omitted during the creation ''POST''.		This example uses default values mostly. Some attributes are given specific values, depending on the needs. There is also required attributes, for which no defaults exist. Here and '''transport_protocol.ip_interface''' and '''transport_protocol.public_ip_address''' are by default empty, and must be set otherwise the ''POST'' will be refused. The attribute ''naps'' is also required to complete the overall configuration, but can be omitted during the creation ''POST'', and added at a later time.
	POST /configurations/{CfgName}/h248_stacks {		POST /configurations/{CfgName}/h248_stacks {
	-> Content: {		-> Content: {