Hi Firas,
I've got the same problem. Did you manage to solve your problem? If yes, how?
Thank You,
Leila
I have this same error.
Let me describe our (purported) configuration first -- please see attached system.txt, config.txt and inap_config.ms7:
The Dialogic stack runs on the "left" side in SCTP server mode.
The file inap_config.ms7 is necessary because the s7_mgt module was unable to configure the INAP module. Without printing any error messages, it silently ignored the INAP_CONFIG section of config.txt. Consequently, the unconfigured INAP module threw away all user messages. The inap_config.ms7 file sets up module ID's, dialogue ID ranges, trace options, and defines the CAMELv3 application context. All requests complete successfully (translated trace):
We try to open a dialogue using the INAP API. The INAP module sends a TC-BEGIN message to the TCAP module, but the TCAP module refuses it with P-Abort. Originally we added one invoke (InitialDP) component to the TC-BEGIN packet, but we encounter the same P-Abort with the "empty" TC-BEGIN as well. The problem is reproducible with s7_play, so that's what I will describe below.
These are the two messages we send to INAP:
First:
Second:
The INAP module confirms both messages (translated log):
And accordingly, it sends the following message to TCAP:
S7L:2009-07-21 17:53:28.083 I0000 T 0000058e M tc783 i4000 f35 d14 r0000 s00 e00000000 p02060102070443ca00920804436500920d070400000115030400
Or, in translated format,
S7L:2009-07-21 17:53:28.083 I0000 T 0000058e M TCP_MSG_DLG_REQ i4000 fINAP dTCAP r0000 s00 e00000000 p02060102070443ca00920804436500920d070400000115030400
Parameters:
(Note that we tried to switch the order of the orig and dest addresses, to no avail.)
Alas, the TCAP module refuses this message (translated log):
Parameters in TCP_MSG_DLG_IND:
The INAP module translates this abort indication for the original user (translated log):
S7L:2009-07-21 17:53:28.084 I0000 T 0000058e M INAP_MSG_DLG_IND i0000 fINAP dUSER r0000 s00 e00000000 p050901000c010100
If we submit the TC-BEGIN message directly to TCAP with s7_play, in order to request confirmation (because the INAP module doesn't requests confirmation), with a different dialogue ID, as in
M-tc783-i5000-fEF-d14-r8000-s00-e00000000-p02060102070443ca00920804436500920d070400000115030400
then the same thing happens as above, but additionally, we receive the following negative confirmation from TCAP (translated):
S7L:2009-07-21 18:27:36.480 I0000 M R:TCP_MSG_DLG_REQ i5000 fTCAP dLOG r0000 s06 e00000000 p02060102070443ca00920804436500920d070400000115030400
Where status 0x06 means TCPE_BAD_PARAM, "Invalid parameters contained in the message".
Could somebody please help with why TCAP finds this TC-BEGIN message invalid? Thank you very much.
We solved the problem. It was caused by the incorrect application context name definition in inap_config.ms7:
M-t77F6-i0050-fEF-d35-r8000-p00000000000000000704000001150304
The corrected version (inserted octets are bold and underlined)
M-t77F6-i0050-fEF-d35-r8000-p00000000000000000BA109060704000001150304
Having no previous Q.773 and X.209 experience, we were misled by a typo in U16SSS12-INAP-PM.pdf. There are two instances of this typo:
There is no such thing as an Object Identifier Name tag. It's either Object Identifier tag (0x06), or Application Context Name Tag (0xA1). We interpreted the typo as the former, but the correct interpretation is the latter. So when defining the application context, one has to encode not only the (contents) of the OID, but the entire Application Context Name constructor:
We realized that the problem was technically caused by our incorrect INAP configuration when we looked at other application context definitions in RUN/INTU/SCRIPTS/inapcfg.ms7 (from upd.tar, V5.00).
Thanks for taking the trouble to mention the typo in the manual. We've marked this up for correction when we next release the manual to avoid confusion for others.