SS7 MAP: ActivateTraceMode - How to "Set User Error: Facility not supported"?
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
|||||||||||||
|
Posted by Steven Vernick on October 6, 2006, 1:20 pm
Please log in for more thread options I am looking at: Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Mobile Application Part (MAP) specification (3GPP TS 29.002 version 6.12.1 Release 6) Page 864, "Figure 25.9/4: Macro Activate_Tracing_VLR". I do not understand the box "Set User Error: Facility not supported". How is this error "set"? On page 320, I see that the ActivateTraceMode operation is defined as: activateTraceMode OPERATION ::= { ARGUMENT ActivateTraceModeArg RESULT ActivateTraceModeRes -- optional ERRORS { systemFailure | dataMissing | unexpectedDataValue | facilityNotSupported | unidentifiedSubscriber | tracingBufferFull} CODE local:50 } However, I haven't been able to figure out what "ERRORS" means. Do I use a TC-U-ERROR to convey the FACILITY_NOT_SUPPORTED? Can someone please tell me where "ERRORS" is defined? Page 376 includes this definition of ActivateTraceModeRes: ActivateTraceModeRes ::= SEQUENCE { extensionContainer [0] ExtensionContainer OPTIONAL, ..., traceSupportIndicator [1] NULL OPTIONAL } So, there's no way to carry the FACILITY_NOT_SUPPORTED reason code in ActivateTraceModeRes. If someone knows of a rail diagram that shows the messages between a VLR and HLR when the VLR responds to ActivateTraceMode with a FacilityNotSupported, could you please point me to that diagram? Any help would be most appreciated. Thanks very much in advance. | |||||||||||||
|
Posted by Holmespundit on October 10, 2006, 9:01 am
Please log in for more thread options Steven... The error is only 'set' in that the responding entity will send an error response back to the requesting entity. It might better be labeled "Error detected: Facility not supported." MAP dictates that the responding entity should send the requesting entity an error response in the form of a TCAP ReturnError component. The ERRORS part of all OPERATION macros is used to specify the errors that may be generated by the responding entity (in ReturnError components) when it receives the associated operation ARGUMENT (in an Invoke component). In answer to your question: No, there is no way to carry the FACILITY_NOT_SUPPORTED reason code in an ActivateTraceModeRes. The ActivateTraceModeRes would be carried in a ReturnResult component. The FACILITY_NOT_SUPPORTED reason code would be carried as the errorCode on a ReturnError component. You may want to search through the overview sections of the MAP specification for TCAP information. There are also a couple of papers on the Holmespun Solutions web site (http://www.holmespun.biz/) that deal with MAP and TCAP subjects. ...Holmespundit Steven Vernick wrote: | |||||||||||||
| Similar Threads | Posted |
| SS7 MAP: ActivateTraceMode - How to "Set User Error: Facility not supported"? | October 6, 2006, 1:20 pm |
| BCMS vu - Error# 1107 | January 10, 2006, 1:24 pm |
| DASS2 Config..DTM304 Error | May 27, 2006, 4:02 pm |
| any idea about this error 'denial event 1097: MFC No Answer' | March 3, 2005, 5:12 am |
| Format of 'user data' sent in GSM networks?? | December 15, 2005, 8:58 am |
| VoiceXML Script error in Envox console when call is made | April 24, 2007, 5:46 am |
| Test INNUA user group form | November 2, 2005, 12:45 pm |
| Need User manual for GT-7169 (LG cordless telephone) | December 25, 2005, 5:46 pm |
>
> Digital cellular telecommunications system (Phase 2+);
> Universal Mobile Telecommunications System (UMTS);
> Mobile Application Part (MAP) specification
> (3GPP TS 29.002 version 6.12.1 Release 6)
>
> Page 864, "Figure 25.9/4: Macro Activate_Tracing_VLR".
>
> I do not understand the box "Set User Error: Facility not supported".
> How is this error "set"?
>
>
> On page 320, I see that the ActivateTraceMode operation is defined as:
>
> activateTraceMode OPERATION ::= {
> ARGUMENT
> ActivateTraceModeArg
> RESULT
> ActivateTraceModeRes
> -- optional
> ERRORS {
> systemFailure |
> dataMissing |
> unexpectedDataValue |
> facilityNotSupported |
> unidentifiedSubscriber |
> tracingBufferFull}
> CODE local:50 }
>
> However, I haven't been able to figure out what "ERRORS" means. Do I
> use a TC-U-ERROR to convey the FACILITY_NOT_SUPPORTED? Can someone
> please tell me where "ERRORS" is defined?
>
>
> Page 376 includes this definition of ActivateTraceModeRes:
>
> ActivateTraceModeRes ::= SEQUENCE {
> extensionContainer [0] ExtensionContainer OPTIONAL,
> ...,
> traceSupportIndicator [1] NULL OPTIONAL
> }
>
> So, there's no way to carry the FACILITY_NOT_SUPPORTED reason code in
> ActivateTraceModeRes.
>
> If someone knows of a rail diagram that shows the messages between a
> VLR and HLR when the VLR responds to ActivateTraceMode with a
> FacilityNotSupported, could you please point me to that diagram?
>
> Any help would be most appreciated.
>
> Thanks very much in advance.
>