TelecomSpace Discussion Forum.
September 08, 2008, 11:06:49 AM
News: Forum upgraded and more features added.
Home Help Search Login Register *
Welcome, Guest. Please login or register.
Did you miss your activation email?
September 08, 2008, 11:06:49 AM

Login with username, password and session length
Members
Total Members: 1448
Latest: nvikas
Stats
Total Posts: 641
Total Topics: 298
Online Today: 46
Online Ever: 74
(April 12, 2008, 08:05:05 AM)
Users Online
Users: 0
Guests: 15
Total: 15
Recent posts
[Yesterday at 10:20:00 PM]

[Yesterday at 01:22:00 PM]

by Anil
[September 04, 2008, 02:21:56 PM]

[September 03, 2008, 03:03:34 AM]

[September 02, 2008, 07:19:15 AM]

[September 02, 2008, 06:53:26 AM]

[September 02, 2008, 05:48:18 AM]

[August 31, 2008, 03:49:28 AM]

by mary
[August 30, 2008, 10:48:33 AM]

by zhah
[August 30, 2008, 10:16:56 AM]
    Pages: [1]   Go Down
    Print
    Author Topic: Application context name  (Read 295 times)
    Maddy
    Newbie
    *
    Offline Offline

    Posts: 13


    View Profile
    « on: June 26, 2008, 05:02:43 AM »

    HI All,
    What is Application Context Name in ss7 MAp ?

    Thanks

    Maddy
    Logged
    pramod
    Newbie
    *
    Offline Offline

    Posts: 27


    View Profile
    « Reply #1 on: June 26, 2008, 06:44:47 AM »

    Hi Maddy
    Application Context comes under dialogue portion of TCAP msg
    Where it specifies about the msg Version and type .

    Logged
    dineshonss7
    Newbie
    *
    Offline Offline

    Posts: 17


    View Profile
    « Reply #2 on: July 15, 2008, 06:48:03 AM »

    Its 8 byte value used to negotiate the service capabality and version supported between MAP users.

    First 6 byte will be almost fixed for all MAP operation code.

    byte[0] = 00  /* CCITT */
    byte[1] = 04  /* Identified organazation */
    byte[2] = 00  /* ETSI */
    byte[3] = 00  /* Mobile Domain */
    byte[4] = 01  /* GSM Network */
    byte[5] = 00  /* AC Id */

    Last two byte differs according to MAP operation code and version supported by MAP layer.
    Sixth byte takes value defined in MAP spec according to operation code which MAP user wants to negotiate with peer.
    Seventh byte contains version supported for that message (operation code).
    byte[6] =  18  /* Network Functional Ss -- example value */
    byte[7] =   2  /* supported version 2 */

    NOTE :- Network Functional Ss conext value is defined for REGISTER SS operation code.
    Logged
    Pages: [1]   Go Up
    Print
    Jump to:  

    Powered by MySQL Powered by PHP Powered by SMF 1.1.3 | SMF © 2006-2007, Simple Machines LLC
    TinyPortal v0.9.7 © Bloc
    Valid XHTML 1.0! Valid CSS!
    Page created in 0.174 seconds with 26 queries.