You are here

INAP operations in separate TCAP messages

3 posts / 0 new
Last post
jHartman
INAP operations in separate TCAP messages

Dear all,

I'm struggling with small problem and unfortunately I cannot find any reasonable answer in specifications:

One of my customers has an exchange which sends INAP operations as separate TCAP messages, for example:

1st example:

Switch SCP
-------- IDP --------->
<---- RRB+CIQ+CON -----
-------- CIR --------->
----- ERB(oBusy) ----->

It's something that seems really strange to me because:

a) I was expecting INAP operations within single TCAP msg, e.g.:

2nd example:

Switch SCP
-------- IDP --------->
<---- RRB+CIQ+CON -----
---- ERB + CIR -------->

b) InvokeIDs for CIR and ERB in 1st example are also assigned in... suspected way: CIR has invokeID=3 and ERB has invokeID=2.

Currently I cannot find any specification that concludes if this flow is correct or incorrect. I've quickly scanned Q.12xx series and apart of some examples (NB similar to 2nd example) I couldn't find anything useful.

I'll appreciate any hint from you.

Thank you in advance and best regards.

pramod
Re:Invokes Id 's will be different

Hi
Invoke id's will be different for different invoke operations.
You can receive all the components in a single T-CAP message or multiple messages for each component.
For each component Invoke id will be different.

jHartman
Re:Invokes Id 's will be different

> b) InvokeIDs for CIR and ERB in 1st example are also assigned in... suspected way: CIR has invokeID=3 and ERB has
> invokeID=2.

Sorry for being not precise - I'm not surprised by different invokeIDs (which is normal). I'm worrying about sequence - its message (CIR) has 3 and subsequent ERB - 2. This would suggest wrong order of messages. Am I right?

> You can receive all the components in a single T-CAP message or multiple messages for each component.

Do you remember any reference to INAP or TCAP specs? To be honest that's something I'm looking for last days.