This section describes the custom server functions supplied with the ISDN single step call transfer application. The purpose of the SSTransfer custom server is to take address information and encode it as ASN.1 encoded data in accordance with the facility message definition in Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001)
Two functions are provided with the SSTransfer custom server:
The SSTransfer custom server issues standard custom server return codes only. It does not issue alarms with a severity color code.
With any of these errors, if you have followed the suggestions in the User Response, and you are unable to solve the problem, contact Blueworx Support. When you call, you will need details of any errors, your system setup, and details of the conditions that cause the problem. You may also require an AIX system trace taken when the problem occurs. Before taking the trace, set the -d option in the custom server. For more information on the command line options see Configuring the SSTransfer custom server
The possible return codes generated by the ISDN single step call transfer, together with explanations and suggested responses, are as follows:
|
Error Code |
Description |
Explanation |
User response |
|---|---|---|---|
|
0 |
Success |
ASN1 has been generated successfully. |
None required |
|
1 |
Transfer to number plan not valid |
The custom server received a number plan value which did not conform to the allowed values in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the number plan setting to an allowed value. |
|
2 |
Transfer to number type not valid |
The custom server received a number type value which did not conform to the allowed values in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the number type setting to an allowed value. |
|
3 |
Transfer to number plan and number type not consistent |
The custom server received number plan and number type values which did not conform to the allowed combinations in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the number plan and number type values to an allowed combination. |
|
4 |
AwaitConnect not set to a valid value |
The custom server received an AwaitConnect parameter value which did not conform to the allowed values in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the AwaitConnect parameter setting to an allowed value. |
|
6 |
Transferred number not present and presentation field does not indicate it should not be present. |
The custom server received no transferred from number value but the transfer from number presentation value indicates that it should be present. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and either add a transferred from number or change the transfer from number to indicate that no transfer from number is required. |
|
7 |
Transferred number presentation field not valid |
The custom server received a transferred number presentation value which did not conform to the allowed values in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the transferred number presentation setting to an allowed value. |
|
8 |
Transferred number presentation and screening fields are inconsistent. |
The custom server received transferred number presentation and screening values which did not conform to the allowed combinations in the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification. |
Review the Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001) specification and change the transferred number presentation and screening type values to an allowed combination. |
|
10 |
Internal error with ASN1 generation |
The custom server has experienced an internal error in its ASN1 generation |
Re-create the problem and take an AIX system trace (specify the –d3 command-line parameter for the custom server), before calling Blueworx Support. |
|
21 |
No transferred number present |
The custom server received tag data that does not contain a transferred number within the CLGN tag. |
Review the tag data that is being passed into the custom server by taking a system-level trace. Correct the tag data as appropriate. |
|
22 |
Unable to determine transferred number’s number plan |
The custom server received tag data that does not contain or does not contain a valid number plan within the CLGN.NUMBER_PLAN tag attribute. |
Review the tag data that is being passed into the custom server by taking a system-level trace. Correct the tag data as appropriate. |
|
23 |
Unable to determine transferred number’s number type |
The custom server received tag data that does not contain or does not contain a valid number type within the CLGN.NUMBER_TYPE tag attribute. |
Review the tag data that is being passed into the custom server by taking a system-level trace. Correct the tag data as appropriate. |
|
24 |
Unable to determine transferred number’s screening value |
The custom server received tag data that does not contain or does not contain a valid number screening value within the CLGN.NUMBER_SCREEN tag attribute. |
Review the tag data that is being passed into the custom server by taking a system-level trace. Correct the tag data as appropriate. |
|
25 |
Unable to determine transferred number’s presentation value |
The custom server received tag data that does not contain or does not contain a valid number presentation value within the CLGN.NUMBER_PRESENT tag attribute. |
Review the tag data that is being passed into the custom server by taking a system-level trace. Correct the tag data as appropriate. |
|
31 |
State table openhostserver failed |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx |
|
32 |
State table senddata failed |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx |
|
33 |
State table receive data failed with no more data error |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx Support. |
|
34 |
State table receive data failed with data not found |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx Support. |
|
35 |
State table receive data failed with host problem |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx Support. |
|
36 |
State table receive data failed with host not open |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx |
|
37 |
State table receive data failed with timeout |
scct_transfer state table error |
Re-create the problem and take an AIX system trace, before calling Blueworx |
|
40 |
State table TransferCall action failed |
An Edge other than Succeeded was returned from the TransferCall action |
Re-create the problem and take an AIX system trace, before calling Blueworx |
Allows calling number addressing details to be supplied in the TAG format captured in SV252, supplied when an incoming call arrives.
char TransferTag_TransfertoNumber[32]
The number to which the call is to be transferred.
short TransferTag_TransfertoNumberPlan
The number plan for the number to which the call is to be transferred.
short TransferTag_TransfertoNumberType
The number type for the number to which the call is to be transferred.
short TransferTag_AwaitConnect
Set to determine when the call should be disconnected, either as soon as transfer is attempted or only after connection is established to the third party. The values are as defined in Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001).
char TransferTag_callingdata[250]
The data as provided in SV252 on the incoming call.
short TransferTag_rc
The return code.
char TransferTag_data[250]
The ASN1 BER encoding of supplied called and calling number parameters.
Allows calling number addressing details to be supplied as separate (number , number plan, and number type) parameters.
char Transfer_TransfertoNumber[32]
The number to which the call is to be transferred.
short Transfer_TransfertoNumberPlan
The number plan for the number to which the call is to be transferred.
short Transfer_TransfertoNumberType
The number type for the number to which the call is to be transferred.
char Transfer_TransferredNumber[32]
The number to set as the number from which the call is transferred.
short Transfer_TransferredNumberScreen
The screening indicator for the number set as the number from which the call is transferred.
short Transfer_TransferredNumberPresent
The presentation indicator for the number set as the number from which the call is transferred.
short Transfer_AwaitConnect
Set to determine when the call should be disconnected, either as soon as transfer is attempted or only after connection is established to the third party. The values are as defined in Single Step Call Transfer (SSCT) Supplementary Service (ECMA-300, edition 2 Dec 2001).
short TransferTag_rc
The return code.
char TransferTag_data[250]
The ASN1 BER encoding of supplied called and calling number parameters.