...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Before the introduction of the Reason Header - Local/Remote Resource Availability feature, if there were no resources available on the outgoing TDM side, the IMG 2020 would respond to the incoming SIP network with a 503 Service Unavailable response. The 503 response sent would not give any indication whether the IMG 2020 itself was out of resources or whether the SS7 network was out of resources. With the introduction of this feature, a user can distinguish whether the 503 Service Unavailable response sent to the SIP network was caused due to a lack of resources on the IMG 2020 or lack of resources in the outgoing SS7 network. Refer to the links in the Related Topics section below.
...
Below are instructions on how to configure the functionality for this feature. Before configuring, an initial configuration must be created on it. Refer to the Basic Configurations procedure and verify the required basic functionality has been configured prior to configuring this feature. Also, the feature is supported when going from a SIP network to an SS7 network which requires both SS7 and SIP signaling to be configured. Refer to the Configure SS7, Configure SIP (Multiple SIP IP) or Configure SIP (Single SIP IP) topics as required.
Configure SIP SGP Profile
...
Right click on the Profiles object and select New SIP Profiles. The SIP Profiles object is a parent or container object and no configuration is required in this object. Refer to the SIP Profiles topic for more information on this object.
Right click on the Profiles object again and select New SIP Profile. The first SIP Profile created is a default profile and cannot be modified. Disregard this profile.
Right click on the Profiles object again and select New SIP Profile. In the Name field, enter a name that describes the SIP Profile being created. In this procedure the SIP Profile was labeled SIP_Prof_ReasonHeader. Refer to SIP Profile - SGP topic for more information on configuring the remaining fields within this object.
Right click on the SIP Profile created and select New SIP Headers. To enable the feature, select Enable in the drop down menu of the Reason-header Local field. Refer to the screen capture below.
...
Right click on the Routing Configuration object and select New Channel Groups. The Channel Groups object is a container object for multiple channel group objects and no configuration is required here. Refer to the Channel Groups topic for more information on this object.
Right click on Channel Groups object and select New Channel Group. In the Name field, enter a name that describes the channel group being created.
Set the Signaling Type field to SIP. Refer to Channel Group topic for more information on configuring the remaining fields in the SIP Channel Group object.
...
Right click on the Dialogic object and select New External Network Elements. The External Network Element pane is a parent or container object and no configuration is required here. Refer to External Network Elements topic for more information on this object.
Right click on the External Network Elements object and select New External Gateways. Again, the External Gateways object is a container or parent object and no configuration is needed here. Refer to External Gateways topic for more information on this object.
Right click on External Gateways object and select New External Gateway. Refer to screen capture below.
...