Best practices - Revision history

Allyntree at 17:47, 3 April 2023

2023-04-03T17:47:22Z

← Older revision		Revision as of 13:47, 3 April 2023
Line 1:		Line 1:
	~~{{DISPLAYTITLE:Best Practices}}~~

	This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.		This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.

Allyntree at 14:01, 20 July 2022

2022-07-20T14:01:58Z

Cbilodeau: change category to gateway oam&p

2013-08-23T17:43:25Z

change category to gateway oam&p

← Older revision		Revision as of 13:43, 23 August 2013
Line 1:		Line 1:
	~~[[Category:Tmedia_OAM%26P]]~~

	This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.		This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.
Line 28:		Line 27:
	*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>		*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>

			[[Category:Gateway_OAM%26P\|Best Practice]]
	[[Category:Tdev_OAM%26P\|Best Practice]]		[[Category:Tdev_OAM%26P\|Best Practice]]

Cbilodeau: add category

2011-02-14T20:00:16Z

add category

← Older revision		Revision as of 16:00, 14 February 2011
Line 27:		Line 27:
	*Probably the most important best practice of all is this: perform backups of your system configuration data on a regular basis. In fact, TelcoBridges recommends that you back up your configurations both before and after modifying them. This can be done within the Web Portal interface via the Backups section in the navigation bar. There you can directly back up the current database as well as view and recover from previous database backups.		*Probably the most important best practice of all is this: perform backups of your system configuration data on a regular basis. In fact, TelcoBridges recommends that you back up your configurations both before and after modifying them. This can be done within the Web Portal interface via the Backups section in the navigation bar. There you can directly back up the current database as well as view and recover from previous database backups.
	*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>		*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>


			[[Category:Tdev_OAM%26P\|Best Practice]]

Cbilodeau: add category tmedia oam&p

2011-02-03T21:42:33Z

add category tmedia oam&p

← Older revision		Revision as of 17:42, 3 February 2011
Line 1:		Line 1:
	~~This page contains some best practices that you should consider adopting when working with a~~ [[~~Tmedia~~]] ~~or [[Tdev]] system and [[Toolpack]].~~		[[Category:Tmedia_OAM%26P]]

			This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.

			= Web Portal =

	== Naming conventions ==		== Naming conventions ==

Ktrueman: content taken from training module 210

2010-07-15T15:44:18Z

content taken from training module 210

New page

This page contains some best practices that you should consider adopting when working with a [[Tmedia]] or [[Tdev]] system and [[Toolpack]].

== Naming conventions ==

When working with any complex system that requires multiple variables to be configured, and especially when working with a system that allows you to create multiple configurations, you need a method for ensuring that you can both create, as well as come back to and revise, system configurations. Most of the time this comes down to the way that system configurations and sub-settings are named.

We have identified a couple of considerations when creating names for your configurations.

#Be consistent in the way that you name and number items, specifically when working with multiple sub-components such as line interfaces, network access points, call routes and others. Whether you choose to use full words to describe system components, or abbreviations, the important thing is to be consistent. The same goes for the use of upper and lower case letters. By the way, TelcoBridges recommends the use of capitals when naming network access points or NAPs. It also important to pay attention to the way that you append numbers to component names; in particular, you need a numbering schema that will allow your system capacity to grow.
#Take good care to ensure that the names that you create are intuitive or as intuitive as they can be if you are using a series of abbreviations. Whenever possible, the names that you create should say what the configuration, or the component or the service is being used for. If the configuration does not use SS7, then make sure that the term SS7 does not appear in the configuration name. Creating intuitive names will help you when you come back 3 months or a year later and need to make modifications. Intuitive naming will also help when you reach out to the TelcoBridges technical support team, particularly if you need them to perform remote intervention on your system.
#Ensure that names are always unique and that no single name is applied to more than one sub-component.
#Document your configuration of the Web Portal using an external tool. Microsoft Excel, while not designed for this purpose, can be a useful tool. You can even create your naming schema and name your components there, then build out your Web Portal configuration based on them.

By following these suggestions, you should be able to simplify the creation of a system configuration on your TelcoBridges device.

<br>

== Configuration Management ==

*While you are not obligated to do so by the system, TelcoBridges strongly recommends that you duplicate a given configuration before attempting to modify it. This can make a major difference should you run into difficulty with a new configuration and need to quickly bring the system back to its original operating state. Due to the high number of variables that need to be configured for a typical telecommunications network device, it is easier and much faster to modify a system that was known to work then to attempt to configure all variables from scratch.
*By maintaining multiple versions of a configuration, with different names or version numbers, you have the ability to roll-back to a given configuration depending on system performance or on changing business requirements. The ability to roll-back is particularly useful if you have just modified a configuration and the modified version does not work.
*Before putting a new or modified configuration in to service, you should first validate it. This step, which takes only a few seconds and involves clicking a single button, will enable you to detect any errors in the configuration.
*Probably the most important best practice of all is this: perform backups of your system configuration data on a regular basis. In fact, TelcoBridges recommends that you back up your configurations both before and after modifying them. This can be done within the Web Portal interface via the Backups section in the navigation bar. There you can directly back up the current database as well as view and recover from previous database backups.
*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>

← Older revision		Revision as of 10:01, 20 July 2022
Line 1:		Line 1:
			{{DISPLAYTITLE:Best Practices}}

	This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.		This page contains some best practices that you should consider adopting when using a [[Tmedia]] system.

	~~= Web Portal =~~

	== Naming conventions ==		== Naming conventions ==
Line 10:		Line 9:
	We have identified a couple of considerations when creating names for your configurations.		We have identified a couple of considerations when creating names for your configurations.

	#Be consistent in the way that you name and number items, specifically when working with multiple sub-components such as line interfaces, network access points, call routes and others. Whether you choose to use full words to describe system components, or abbreviations, the important thing is to be consistent. The same goes for the use of upper and lower case letters. ~~By the way,~~ TelcoBridges recommends the use of capitals when naming network access points or NAPs. It also important to pay attention to the way that you append numbers to component names; in particular, you need a numbering schema that will allow your system capacity to grow.		#Be consistent in the way that you name and number items, specifically when working with multiple sub-components such as line interfaces, network access points, call routes and others. Whether you choose to use full words to describe system components, or abbreviations, the important thing is to be consistent. The same goes for the use of upper and lower case letters. TelcoBridges recommends the use of capitals when naming network access points or NAPs. It also important to pay attention to the way that you append numbers to component names; in particular, you need a numbering schema that will allow your system capacity to grow.
	#Take good care to ensure that the names that you create are intuitive or as intuitive as they can be if you are using a series of abbreviations. Whenever possible, the names that you create should say what the configuration, or the component or the service is being used for. If the configuration does not use SS7, then make sure that the term SS7 does not appear in the configuration name. Creating intuitive names will help you when you ~~come back~~ 3 months or a year later and need to make modifications. Intuitive naming will also help when you reach out to the TelcoBridges technical support team, particularly if you need them to perform remote intervention on your system.		#Take good care to ensure that the names that you create are intuitive or as intuitive as they can be if you are using a series of abbreviations. Whenever possible, the names that you create should say what the configuration, or the component or the service is being used for. If the configuration does not use SS7, then make sure that the term SS7 does not appear in the configuration name. Creating intuitive names will help you when you return 3 months or a year later and need to make modifications. Intuitive naming will also help when you reach out to the TelcoBridges technical support team, particularly if you need them to perform remote intervention on your system.
	#Ensure that names are always unique and that no single name is applied to more than one sub-component.		#Ensure that names are always unique and that no single name is applied to more than one sub-component.
	#Document your configuration of the Web Portal using an external tool. Microsoft Excel, while not designed for this purpose, can be a useful tool. You can even create your naming schema and name your components there, then build out your Web Portal configuration based on them.		#Document your configuration of the Web Portal using an external tool. Microsoft Excel, while not designed for this purpose, can be a useful tool. You can even create your naming schema and name your components there, then build out your Web Portal configuration based on them.
Line 21:		Line 20:
	== Configuration Management ==		== Configuration Management ==

	*While you are not obligated to do so by the system, TelcoBridges strongly recommends that you duplicate a given configuration before attempting to modify it. This can make a major difference should you run into difficulty with a new configuration and need to quickly bring the system back to its original operating state. Due to the high number of variables that need to be configured for a typical telecommunications network device, it is easier and much faster to modify a system that was known to work ~~then~~ to attempt to configure all variables from scratch.		*While you are not obligated to do so by the system, TelcoBridges strongly recommends that you duplicate a given configuration before attempting to modify it. This can make a major difference should you run into difficulty with a new configuration and need to quickly bring the system back to its original operating state. Due to the high number of variables that need to be configured for a typical telecommunications network device, it is easier and much faster to modify a system that was known to work than to attempt to configure all variables from scratch.
	*By maintaining multiple versions of a configuration, with different names or version numbers, you have the ability to roll-back to a given configuration depending on system performance or on changing business requirements. The ability to roll-back is particularly useful if you have just modified a configuration and the modified version does not work.		*By maintaining multiple versions of a configuration, with different names or version numbers, you have the ability to roll back to a given configuration depending on system performance or on changing business requirements. The ability to roll back is particularly useful if you have just modified a configuration and the modified version does not work.
	*Before putting a new or modified configuration in to service, you should first validate it. This step, which takes only a few seconds and involves clicking a single button, will enable you to detect any errors in the configuration.		*Before putting a new or modified configuration in to service, you should first validate it. This step, which takes only a few seconds and involves clicking a single button, will enable you to detect any errors in the configuration.
	*Probably the most important best practice of all is this: perform backups of your system configuration data on a regular basis. In fact, TelcoBridges recommends that you back up your configurations both before and after modifying them. This can be done within the Web Portal interface ~~via~~ the Backups section in the navigation bar. There you can directly back up the current database as well as view and recover from previous database backups.		*Probably the most important best practice of all is this: perform backups of your system configuration data on a regular basis. In fact, TelcoBridges recommends that you back up your configurations both before and after modifying them. This can be done within the Web Portal interface using the Backups section in the navigation bar. There you can directly back up the current database as well as view and recover from previous database backups.
	*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>		*Finally, TelcoBridges recommends that following the creation or modification of a system configuration and its subsequent backup on the media gateway or telecom platform device, that you download an offline archive of the configuration database for safe-keeping.<br>

	[[Category:Gateway_OAM%26P\|Best Practice]]		[[Category:Gateway_OAM%26P\|Best Practice]]
	[[Category:Tdev_OAM%26P\|Best Practice]]		[[Category:Tdev_OAM%26P\|Best Practice]]