M3UA Destination Available - MTP-Pause

[Shardik]

Hi everyone,

I am using Restcomm SS7 to develop an SMS Gateway. I am working over SIGTRAN.
I noticed that whenever I receive DAVA from adjacent PC: (extract from wireshark)

MTP 3 User Adaptation Layer
    Version: Release 1 (1)
    Reserved: 0x00
    Message class: SS7 signalling network management messages (2)
    Message type: Destination available (DAVA) (2)
    Message length: 24
    Affected point code (1 destination)
        Parameter Tag: Affected point code (18)
        Parameter length: 8
        Mask: 0
        Affected point code: 230
    Routing context (1 context)
        Parameter Tag: Routing context (6)
        Parameter length: 8
        Routing context: 100

Restcomm SS7 stack translates it into MTP-PAUSE Primitive:

10:47:38,542 WARN  [SccpStackImpl-SccpStack] (pool-16-thread-1) Rx : MTP-PAUSE: AffectedDpc=230

I am new to SS7/SIGTRAN world, so maybe I am completely wrong, but I was expecting to see an MTP-RESUME primitive, right?

Thanks for your much appreciated work!

Regards,
Filippo

[huu nhan Tran]

It's normal log,
What's your problem?
Your message can't hit destination or you can't receive return message?

Restcomm has opensource SMSC GW at https://github.com/RestComm/smscgateway
I think telestax is preparing for next release in nextweek with many new feature :) you can contribute to them instead of write brand new SMSC GW (10 years)


BR,
TN

[Shardik]

Looking forward to Restcomm SMSC, I will be happy to contribute!

However, my problem is that when I receive DAVA from SGW I expect to see it mapped into MTP-RESUME for MTP-user, instead of MTP-PAUSE:

DAVA --> MTP-RESUME
DUNA --> MTP-PAUSE

Am I right?

[Shardik]

I checked code on https://github.com/RestComm/jss7/blob/master/m3ua/impl/src/main/java/org/mobicents/protocols/ss7/m3ua/impl/SignalingNetworkManagementHandler.java:


AspState aspState = AspState.getState(fsm.getState().getName());
 
if (aspState == AspState.ACTIVE) {
 AffectedPointCode affectedPcObjs = dava.getAffectedPointCodes();
 int[] affectedPcs = affectedPcObjs.getPointCodes();
 for (int i = 0; i < affectedPcs.length; i++) {
  Mtp3PausePrimitive mtpPausePrimi = new Mtp3PausePrimitive(affectedPcs[i]);
  ((AsImpl) aspImpl.getAs()).getM3UAManagement().sendPauseMessageToLocalUser(mtpPausePrimi);
 }
} else {
 logger.error(String.format("Rx : DAVA for RoutingContext=%d. But ASP State=%s. Message=%s", rcs[count], aspState, dava));
}

Instead of MtpPausePrimitive, I was expecting an MtpResumePrimitive. Am I right?

[huu nhan Tran]

It look like the configuration problem,
Can you please attach pcap file and server.log


BR,
TN

[Shardik]

Attached wireshark capture, server.log and SS7 configuration files.

Best Regards,
Filippo

[Shardik]

Hello everyone,

I have built and currently trying newer RestComm SMSC version and wow, awesome job guys!

However Using SS7 3.0.1329 I am experiencing the same issue regarding treatment for Sigtran DAVA messages received when remote endpoint becomes available: these messages are still sent to M3UA-user layers as MTP-PAUSE messages.
I still don't know if I am doing something wrong in my configuration, or if that's a bug.

Attached my new SS7 config files.

Can you help me?

Best regards and keep up with the good work!