JSS7 - TC-CONTINUE: No dialog/transaction for id:

Question

We are working on SS7 CAMEL application. The application is based on jboss 5.10GA and Mobicents/Restcomm's jss7 and Restcomm's CAP Resource adapter.

In our Sbb we receive InitialDP message and delimiter from switch. After we recieve the delimiter we try to send connect message to the switch.

Unfortunatelly, when we invoke .send() method on the dialog that we receive in onDelimiter method, no message to switch is sent and what we can see in the jboss log is:

TC-CONTINUE: No dialog/transaction for id: 67793592

    public void onDelimiter(DialogDelimiter delimiter, ActivityContextInterface aci) 
    {
        try
        {
            CAPDialogCircuitSwitchedCall dialog = (CAPDialogCircuitSwitchedCall) delimiter.getCAPDialog();
            dialog.addRequestReportBCSMEventRequest(bcsmevents, extensions);
            dialog.addCallInformationReportRequest(requestsTypes, null, null);
            dialog.addConnectRequest(new DestinationRoutingAddressImpl(new ArrayList<CalledPartyNumberCap>(Arrays.asList(new CalledPartyNumberCapImpl(new CalledPartyNumberImpl("48602465380".getBytes()))))), null, new OriginalCalledNumberCapImpl(new OriginalCalledNumberImpl(cdr.getBNumber().substring(0,10).getBytes())), null, new CarrierImpl("9191".getBytes()), null, null, null, null, null, null, null, null, false, false, false, null, false);
            dialog.addContinueRequest();
            dialog.send();
            (...)
         }
     }

If it is a problem with our sccp rules then what should be the correct sccp settings for the following addresses:

Switch: PC: 6801, SSN: 146, GT: 4794733271, AI: 18

Our server: PC: 5100, SSN: 146, GT: 442080000100, AI: 18

Here's the boot.log file

Here's the server.log file

can you please share the logs? – Waqas Apr 25 '16 at 08:58 — Waqas, Apr 25 '16 at 08:58

score 2 · Answer 1 · answered May 02 '16 at 19:53

2

This message "TC-CONTINUE: No dialog/transaction for id: 67793592" means that a TC-CONTINUE primitive came to TCAP stack but no such local dialog. No processing was done and onDelimiter() method was not invoked.

The most probably reason is that the TCAP dialog was already timeed out. You need : - either increase dialogTimeout stack options (many times because it is CAP) - or inside "CAPDialogListener.onDialogTimeout(CAPDialog capDialog)" invoke capDialog.keepAlive(); (this way you need to check if dialog is not kept for too long time)

answered May 02 '16 at 19:53

Sergey Vetyutnev

71
1

When I try to register to CAPProvider I get: java.lang.UnsupportedOperationException at org.mobicents.slee.resource.cap.wrappers.CAPProviderWrapper.addCAPDialogListener(CAPProviderWrapper.java:71) Here's how I create an instance of CAPProvider: Context ctx = (Context) new InitialContext().lookup("java:comp/env"); CAPProvider provider = (CAPProvider) ctx.lookup("slee/resources/cap/2.0/provider"); CAPProvider that I get is an instance of CAPProviderWrapper. Is there a way to get CAPProvider that is an instance of CAPProviderImpl or maybe I am missing something else? – B. Barylowicz May 10 '16 at 09:02

score 1 · Answer 2 · answered May 02 '16 at 14:37

1

I think you are using Restcomm jainslee with cap RA?

Can you please attach server.log?

Br,

TN

answered May 02 '16 at 14:37

huu nhan Tran

31
2

Yes, I am using Restcomm jainslee with CAP RA. I attached the logs from jboss to the original message – B. Barylowicz May 10 '16 at 09:13
Hi,Sorry for late. but the Dialog of Delimeter() was close after your application receive this message. The idea is create new Dialog and and send back – huu nhan Tran May 28 '16 at 06:23
Unfortunately, in our solution the dialog can be initiated only on the switch side. So we are unable to create new dialog on out side. – B. Barylowicz Jun 03 '16 at 07:43
I think Delimiter message come in a TCAP-END so the dialog closed and you can't send back any other message. Can you check it in your pcap file – huu nhan Tran Jun 05 '16 at 13:13

JSS7 - TC-CONTINUE: No dialog/transaction for id:

2 Answers2