Disclaimer: These archives are mirrored from smsforum.net in 2007 before the forum got closed. Please only part of the forum is available here.
For any clarifications regarding these archives you can contact us at http://www.telecomspace.com/contact.


+  SMS Forum Online Discussion
|-+  SMS Technologies
| |-+  ANSI-41 (CDMA & TDMA) Related (Moderator: SMS Forum Support)
| | |-+  Invoke ID in TCAP
« previous next »
Pages: [1] Go Down Print
Author Topic: Invoke ID in TCAP  (Read 526 times)
Sr. Member
Offline Offline

Posts: 44

« on: May 23, 2006, 10:44:47 UTC »

Can someone please explain the role of Invoke ID in TCAP message

Full Member
Offline Offline

Posts: 20

« Reply #1 on: May 23, 2006, 12:02:50 UTC »

Hi nomi,
            As per document Q773 the description of invoke id is as follow:

An Invoke Component has one or two Component IDs: an Invoke ID, and if it is desired to associate
the Invoke with a previous Invoke, then the Linked ID is provided in addition to the Invoke ID.
Return Result and Return Error Components have one Component ID, called an Invoke ID which is
the reflection of the Invoke ID of the Invoke Component to which they are responding.
The Reject Component uses as its Invoke ID, the Invoke ID in the Component being rejected. If this
ID is unavailable (e.g. due to mutilation of the message undetected by lower layers), then the Invoke
ID tag is replaced with a universal NULL tag (which always has length = 0) as shown in Table 21.
If an Invoke containing both Invoke and Linked IDs is being rejected, only the Invoke ID is used in
the Reject Component.

Hope it will helpful.

Pages: [1] Go Up Print 
« previous next »
Jump to:  

Login with username, password and session length