You are here

Application context name not supported

8 posts / 0 new
Last post
Hamadi
Application context name not supported

Hi all,
In this part of trace, TC-ABORT cause is Application Context Name Not Supported.
It is the roaming between our network and a partner.
the partner use map v2 in his HLR and we use map v3.

some one can help me to find solution at this problem.

00110100 Length Ind 52
[67] TC-ABORT
-------- [49] DTID - Destination Transaction ID 00 4E 07 30
[6B] Abort cause
[28] Dialogue response
[06] Dialogue As Id
00000000 Authority 0 Itu-t (0) recommendation (0)
00010001 Recommendation 17 Q (17)
-------- Number 1414 Q773 (773)
00000001 As 1 Abstract Syntax (1)
00000001 Dialog 1 Dialog-as (1)
00000001 Version 1 Version 1 (1)
[A0] Tag field
[61] Single ASN 1 type
-------- [80] Protocol version 07 80
[A1] Tag field
[06] Application Context Name
00000100 Authority 4 Itu-t (0) identified-organization (4)
00000000 Organization 0 ETSI (0)
00000000 Common domain 0 Mobile Domain (0)
00000001 Mobil Sub Domain 1 GSM Network (1)
00000000 Application Context 0 Application Context GSM Network (0)
00001110 AC GSM Network 14 Information Retrieval (14)
00000010 Version 2 Version 2 (2)
[A2] Tag field
00000001 [02] Associate result 1 Reject Permanent
[A3] Result source diagnostic
[A1] Tag field
00000010 [02] Dialogue service user 2 Application Context Name Not Supported

admin
Application context name not supported

Hi Hamadi,

You will need to use MAPV2 to send the request as the target subsystem is not capable of MAPV3.
Downward compatibility is there but not upward for MAP versions.

As per your traces, the responding HLR also indicated the AC it supports:
++++++++++++++++++++++++++++++++++
[A1] Tag field
[06] Application Context Name
00000100 Authority 4 Itu-t (0) identified-organization (4)
00000000 Organization 0 ETSI (0)
00000000 Common domain 0 Mobile Domain (0)
00000001 Mobil Sub Domain 1 GSM Network (1)
00000000 Application Context 0 Application Context GSM Network (0)
00001110 AC GSM Network 14 Information Retrieval (14)
00000010 Version 2 Version 2 (2)
++++++++++++++++++++++++++++++++++

So, use the above AC to send the request, and it should work if the MAP Operation you are trying to send is supported in MAP V2.

Keep us posted with your progress!

Hamadi
Thank you Admin I would

Thank you Admin
I would inform you of the suite!!!!!

Hamadi
Hi Admin, The target

Hi Admin,
The target subsystem support the MAPV3(information in his IR21).
when the LU is OK, the responding HLR is in MAPV3
but when the LU is falling, the responding HLR is in MAPV2.
it is normal to use Sometimes V3 and Sometimes V2?

admin
Are the responding HLRs are

Are the responding HLRs are different in both cases?

Hamadi
The responding HLRs are

The responding HLRs are different,
in MAPV2 LU is OK
but in MAPV3. the responding HLR is Application context name not supported and the LU is falling,

admin
Please re-read my first

Please re-read my first post.
That means the HLR is not supporting your MAP Version.

Hamadi
Ok, thank you.

Ok, thank you.