testing ussd gateway

[Mncedisi Kasper]

Hi Guys,

Just spent two days trying to test my ussd gateway with no luck, some assistance would be appreciated. I've managed to compile and deploy successfully

When I run the simulator, however, I get a repeated log message as below, I however never get a response back from ussd gateway.

57948 [Thread-1] DEBUG org.mobicents.protocols.sctp.AssociationImpl  - Tx : Ass=Ass_main PayloadData [dataLength=164, complete=true, unordered=false, payloadProtocolId=3, streamNumber=2, data=
Start: 0 (0x00)  End: 163 (0xA3)  Length: 164 (0xA4)

57948 [Thread-1] DEBUG org.mobicents.protocols.sctp.AssociationImpl  - Rx : Ass=Ass_main PayloadData [dataLength=164, complete=true, unordered=false, payloadProtocolId=3, streamNumber=2, data=
Start: 0 (0x00)  End: 163 (0xA3)  Length: 164 (0xA4)

I would really appreciate some help, I've attached my config and server log.

Regards

[Ibrahima Gaye]

Hi,

what about the configs on simulator side ?

------
Ibrahim

--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mncedisi Kasper]

Hi Ibrahim,

I've attached all the config from the simulator data folder, your help will be really appreciated.

Regards

[James Carpenter]

Not sure if it helps, but I noticed in your SCTPManagement_sctp.xml the SERVER association lists hostAddress="". Really don't know if it matters, as I've been rummaging the internet looking for a clue, even trying to track down the maxConcurrentConnectionsCount="0" to see if that was accurate. I would put host address as loopback and see what happens. All the other configs look good based on other samples on the net. Next weekend I will have time to build one and see. Hope it helps.

[Mncedisi Kasper]

Hi James.

Just updated the host address and still get the same problem.

Appreciate the help though.

Regards

[Ibrahima Gaye]

I will look nat it latrer and let you know,

Best regards

------
Ibrahim

[Ibrahima Gaye]

Hello,

on the simulator set your dpc to 1 and your opc to 2

Best regards

------
Ibrahim

[Mncedisi Kasper]

Hi Ibrahim.

I just did, but now I get the error

ERROR org.mobicents.protocols.ss7.m3ua.impl.M3UAManagementImpl  - Tx : No AS found for routing message TransferMessage: {528=Protocol opc=1 dpc=2 si=3 ni=2 sls=1}

What I find interesting though is that the error message "opc=1", "dpc=2", even though I've changed them in the simulator, I need to debug a bit to see why the new values are not being set.

I've attached a screenshot of the changes, and the config file as well to show the changes have been effected (also restarted both the server and the simulator), but I still get the same error.

Regards

[Ibrahima Gaye]

Hello that's a step forward,

because before you were sending the messages to simulator itself;

let me check this error and let you know ...

Regards

------
Ibrahim

[Ibrahima Gaye]

There are  still have some routing issues in your config files (remotespc - set it to 1,, localspc - set it to 2, ...);

it's better you keep it simple at the beginning ou can keep the msisdn.

Hope that will help you,

Best regards,

------
Ibrahim

[Mncedisi Kasper]

Hi Ibrahim.

Thanx so much, that  seems to have been a step closer, now I see the message being sent to the server, but on the server I get an error that shows there's no getDialogLock() method on the TCAP jars included on mobicents-ussd-gateway/lib. I've also verified using jd-gui that the jars tcp jars don't contain this method either in the API or the implementation.

 These are the version of the jars

tcap-api-2.0.0-20121126.011007-18.jar
tcap-impl-2.0.0-20121126.011015-15.jar

I'm checking running mvn clean install on jss7/tcap as this implementation contains the getDialogLock() method.

06:29:34,780 ERROR [STDERR] (pool-29-thread-1) java.lang.NoSuchMethodError: org.mobicents.protocols.ss7.tcap.api.tc.dialog.Dialog.getDialogLock()Ljava/util/concurrent/locks/ReentrantLock;
06:29:34,780 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.map.MAPProviderImpl.onTCBegin(MAPProviderImpl.java:656)
06:29:34,780 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.deliver(TCAPProviderImpl.java:271)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.tcap.DialogImpl.processBegin(DialogImpl.java:1195)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.onMessage(TCAPProviderImpl.java:583)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl.routeMssgFromMtp(SccpRoutingControl.java:132)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.sccp.impl.SccpStackImpl.onMtp3TransferMessage(SccpStackImpl.java:735)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at org.mobicents.protocols.ss7.mtp.Mtp3UserPartBaseImpl$MsgTransferDeliveryHandler.run(Mtp3UserPartBaseImpl.java:263)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
06:29:34,781 ERROR [STDERR] (pool-29-thread-1)     at java.lang.Thread.run(Thread.java:745)

Regards

[Mncedisi Kasper]

Hi Ibrahim,

I got the versioning issue sorted, I copied tcap-api-2.1.0.FINAL.jar and tcap-api-2.1.0.FINAL.jar, statistics-api-2.1.0.FINAL.jar and statistics-api-2.1.0.FINAL.jar into the mobicents-ussd-gateway/lib folder.

Now I have a new problem now, I still don't get the response on the simulator, but I get a warning on the server "Received SccpMessage for Translation but no matching Rule found for local routing".

07:15:54,906 INFO  [TestServlet] (http-127.0.0.1-8080-1) doPost. HttpSession=F470F32CF0FE79FDFD907D0518B81096 Dialog = Dialog [destReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111133], origReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111122], mapMessage=ProcessUnstructuredSSRequest [, ussdDataCodingSch=CBSDataCodingScheme [Code=15, CBSDataCodingGroup=GeneralGsm7, NationalLanguageShiftTable=LanguageUnspecified, CharacterSet=GSM7], ussdString=*519#], msisdn=ISDNAddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=79992222222]], type=BEGIN, id=3]
07:15:54,907 INFO  [TestServlet] (http-127.0.0.1-8080-1) Received ProcessUnstructuredSSRequestIndication USSD String=*519#
07:15:54,913 WARN  [SccpRoutingControl] (pool-24-thread-1) Received SccpMessage for Translation but no matching Rule found for local routing
SccpMessage=Sccp Msg [Type= sls=3 incomingOpc=-1 incomingDpc=-1 outgoingDpc=-1 CallingAddress(pc=1,ssn=8,AI=67,gt=null) CalledParty(pc=0,ssn=8,AI=18,gt=GT0100{tt=0, np=ISDN_TELEPHONY, na=INTERNATIONAL, digits=1111111222}) DataLen=125]

Regards

[Mncedisi Kasper]

Hi,

I am suspecting it might be related to the fact that I could not run the following commands on sccp (of course I could be wrong) :-)
but if not, would someone have an idea why these commands are failing when they are supported according to the User Guide? I will continue to debug the command-line interface to trace.

mobicents(local)>sccp address create 1 82 1 8 0 1 4 000
Invalid Command
mobicents(local)>sccp address create 2 82 2 8 0 1 4 000
Invalid Command
mobicents(local)>sccp rule create 1 K 82 0 8 0 1 4 * solitary 1 origination-type localOriginated
For input string: "origination-type"
mobicents(local)>sccp rule create 2 K 82 0 8 0 1 4 * solitary 2 origination-type remoteOriginated
For input string: "origination-type"
mobicents(local)>

[Mncedisi Kasper]

OK,

Made more progress, I'm not getting to the ussddemo app, just still not getting responses.
I get an error on the server "Received Continue primitive, but state is not proper: InitialReceived, Dialog" and I have no clue what it means. Someone also had a similar error which he solved by updating the latest code, but I have no clue what was updated. I've updated a lot as it is, so any help would be really appreciated.

08:02:29,734 INFO  [HttpClientSbbImpl] (pool-20-thread-1) Created HTTP Activity 'org.mobicents.client.slee.resource.http.HttpClientActivityImpl@99b2563'
08:02:29,737 INFO  [TestServlet] (http-127.0.0.1-8080-1) doPost. HttpSession=BD609EE6EB0EF46C17C375E5BE7709E4 Dialog = Dialog [destReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111133], origReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111122], mapMessage=ProcessUnstructuredSSRequest [, ussdDataCodingSch=CBSDataCodingScheme [Code=15, CBSDataCodingGroup=GeneralGsm7, NationalLanguageShiftTable=LanguageUnspecified, CharacterSet=GSM7], ussdString=*519#], msisdn=ISDNAddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=79992222222]], type=BEGIN, id=3]
08:02:29,738 INFO  [TestServlet] (http-127.0.0.1-8080-1) Received ProcessUnstructuredSSRequestIndication USSD String=*519#
08:02:29,751 ERROR [DialogImpl] (pool-20-thread-1) Received Continue primitive, but state is not proper: InitialReceived, Dialog: org.mobicents.protocols.ss7.tcap.DialogImpl@58ae8aee: Local[3] Remote[3], LocalAddress[pc=1,ssn=8,AI=67,gt=null] RemoteAddress[pc=0,ssn=8,AI=18,gt=GT0100{tt=0, np=ISDN_TELEPHONY, na=INTERNATIONAL, digits=1111111222}]
08:02:29,753 ERROR [MAPStackImpl-"MAPStack"] (pool-20-thread-1) MAP Dialog not found for Dialog Id 3
08:02:29,757 WARN  [HttpClientSbbImpl] (pool-20-thread-1) Rx : DialogProviderAbort DialogProviderAbort [abortProviderReason=ProviderMalfunction, abortSource=TCProblem, extensionContainer=null, MAPDialogSupplementaryWrapper [wrappedDialog=MAPDialog: LocalDialogId=3 RemoteDialogId=3 MAPDialogState=EXPUNGED MAPApplicationContext=MAPApplicationContext [Name=networkUnstructuredSsContext, Version=version2, Oid=0, 4, 0, 0, 1, 0, 19, 2, ] TCAPDialogState=Expunged]]

[Mncedisi Kasper]

Updated previous comment to " I'm now getting to the ussddemo app" instead of "I'm not getting to the ussddemo app"
OK,


Made more progress, I'm now getting to the ussddemo app, just still not getting responses.

[Ibrahima Gaye]

Maybe people may help you better if your share logs on both client and server side :) 

and optionally the config files :)

regards

------
Ibrahim

--

[Mncedisi Kasper]

Oops, I've attached the server logs and config for bot the server and the client.

Regards

[James Carpenter]

Morning,

You may be correct, assuming you are referring to this post. However, based on his data and your's a couple possible issues jump out at me. First, are you using version 2.1.0? i.e. in your server deploy folder what versions are the jars?

Notice the excerpt from the other example below. The differences I noticed, although different test case, are:

• Remote and Local Addresses have the same AI=18
• Remote and Local Addresses have the same gt=GTP0100, whereas yours differ.

Not sure if this helps, but we hope you can push through it. I'll be able to build it and test my guesses this weekend :)   

org.mobicents.protocols.ss7.tcap.api.TCAPException: Received Continue primitive, but state is not proper: Expunged, Dialog: org.mobicents.protocols.ss7.tcap.DialogImpl@6953dc4b: Local[4999] Remote[null], LocalAddress[pc=0,ssn=8,AI=18,gt=GT0100{tt=0, np=ISDN_TELEPHONY, na=INTERNATIONAL, digits=84980200606}] RemoteAddress[pc=0,ssn=8,AI=18,gt=GT0100{tt=0, np=ISDN_TELEPHONY, na=INTERNATIONAL, digits=84980200309}]
    at org.mobicents.protocols.ss7.tcap.DialogImpl.processContinue(DialogImpl.java:1295)

[Sergey Vetyutnev]

Hello,

SCTPManagement_sctp.xml:

<servers>

<server name="serv1" started="true" hostAddress="127.0.0.1" hostPort="8012" ipChannelType="0" acceptAnonymousConnections="false" maxConcurrentConnectionsCount="0" extraHostAddresseSize="0">

<associations>

<string value="ass1"/>

</associations>

</server>

</servers>

<associations>

<name value="Assoc1"/>

<association name="Assoc1" assoctype="CLIENT" hostAddress="127.0.0.1" hostPort="8011" peerAddress="127.0.0.1" peerPort="8012" serverName="" ipChannelType="0" extraHostAddresseSize="0"/>

<name value="ass1"/>

<association name="ass1" assoctype="SERVER" hostAddress="" hostPort="0" peerAddress="127.0.0.1" peerPort="8011" serverName="serv1" ipChannelType="0" extraHostAddresseSize="0"/>

</associations>

You have two associations, one of the CLIENT another is SERVER. So Assoc1 will connect to ass1 just after the server start and no more possible connection outside the server.

If your target is to play with ss7 simulator you need to leave only one association and configure the simulator to tonnect to it.

[Mncedisi Kasper]

Hi James.

Yeah, I updated to 2.1.0 on the USSDGateway deploy folder (the simulator was already on 2.1.0), so the jars on both are the same versions now.

The only impact that had was that I get a fancier version of the same error, but still investigating. I'm hoping I can fix it before the weekend to save you sometime :-)

20:25:08,565 INFO  [TestServlet] (http-127.0.0.1-8080-1) doPost. HttpSession=DC1BA6F829F267E49CD78A40020C1438 Dialog = Dialog [destReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111133], origReference=AddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=1111122], mapMessage=ProcessUnstructuredSSRequest [, ussdDataCodingSch=CBSDataCodingScheme [Code=15, CBSDataCodingGroup=GeneralGsm7, NationalLanguageShiftTable=LanguageUnspecified, CharacterSet=GSM7], ussdString=*519#], msisdn=ISDNAddressString[AddressNature=international_number, NumberingPlan=ISDN, Address=79992222222]], type=BEGIN, id=1]
20:25:08,567 INFO  [TestServlet] (http-127.0.0.1-8080-1) Received ProcessUnstructuredSSRequestIndication USSD String=*519#
20:25:08,671 WARN  [TCAPProviderImpl] (pool-23-thread-1) TC-CONTINUE: No dialog/transaction for id: 7
20:25:08,679 WARN  [HttpClientSbbImpl] (pool-22-thread-1) Rx : DialogProviderAbort DialogProviderAbort [abortProviderReason=SupportingDialogueTransactionReleased, abortSource=TCProblem, extensionContainer=null, MAPDialogSupplementaryWrapper [wrappedDialog=MAPDialog: LocalDialogId=1 RemoteDialogId=7 MAPDialogState=EXPUNGED MAPApplicationContext=MAPApplicationContext [Name=networkUnstructuredSsContext, Version=version2, Oid=0, 4, 0, 0, 1, 0, 19, 2, ] TCAPDialogState=Expunged]]

[Ibrahima Gaye]

Hi,

in yyour ussdgw root pom.xml what is the <ss7.version> value ?

------
Ibrahim

--

[Mncedisi Kasper]

Hi Sergey,

That definitely explains the bind exception I was seeing on the server side, I still could get the messages from simulator though if I started the simulator first. Which then means the bind exception was for the client association trying to connect.

I've now removed the CLIENT association and my simulator can now connect even if I start the server up first (helps a lot in terms of time), appreciate the help.

It still does not solve my main problem though, which is the DialogState moving to Expunged. I still don't know what's causing it, but it fails in org.mobicents.protocols.ss7.tcap.DialogImpl.processContinue.
For some reason it seems that the DialogType.CONTINUE initiated by the TestServlet is not setting correct state...not sure yet, still need to investigate.

20:25:08,671 WARN  [TCAPProviderImpl] (pool-23-thread-1) TC-CONTINUE: No dialog/transaction for id: 7

20:25:08,679 WARN  [HttpClientSbbImpl] (pool-22-thread-1) Rx : DialogProviderAbort DialogProviderAbort [abortProviderReason=SupportingDialogueTransactionReleased, abortSource=TCProblem, extensionContainer=null, MAPDialogSupplementaryWrapper [wrappedDialog=MAPDialog: LocalDialogId=1 RemoteDialogId=7 MAPDialogState=EXPUNGED MAPApplicationContext=MAPApplicationContext [Name=networkUnstructuredSsContext, Version=version2, Oid=0, 4, 0, 0, 1, 0, 19, 2, ] TCAPDialogState=Expunged]]


Regards

[Mncedisi Kasper]

Hi Ibrahim.

On the code checked out here (http://code.google.com/p/ussdgateway/source/checkout ) ss7.version=2.0.0-SNAPSHOT

I, however, tried to change it to 2.1.0-FINAL, but it failed dismally as not all the dependencies in core/bootstrap/pom.xml and

The easiest way was to copy the 2.1.0-FINAL available jars from the JSS7 checked out here ( http://code.google.com/p/jss7/source/checkout), which I had already compiled.

If there's an easier way to update the USSD Gateway from http://code.google.com/p/ussdgateway/source/checkout I'd appreciate the suggestion.

Regards

[Ibrahima Gaye]

I don't know if that's the reason but i would suggest you to face the challenge and update all to 2.1.0.FINAL :)

i did it once for challenge maybe i can provide help if needed.

You can start by setting in the root pom the version 2.1.0.FINAL and resolve dependencies one by one

Best regards

------
Ibrahim

[Mncedisi Kasper]

Hi Ibrahim.

That was on my todo list as soon as I sorted out this issue, but I have to agree with you that that might be the most appropriate course.
This exercise will probably take me a while, so I'll probably feedback on Monday/Tuesday.

Regards

[James Carpenter]

Morning,

As I have pulled my hair out in the past, compiling jss7 2.1.0.FINAL I thought I'd chime in. This is how I got jss7 2.1.0.FINAL to compile (mostly revolved around libmobicents and jmxtools). As usual, let us know if you need more info, and as Ibrahim said, logs, configurations, and data will help those with little time to help you better. Let the data speak for itself :)

There seem to be two current issues with jss7 2.1.0.FINAL.

1. The build will error in core/bootstrap/pom.xml and core/sgw/boot/pom.xml ---> For me, this was due to libmobicents-dahdi-2.1.0.FINAL not existing. There are several ways around this. 

• a. If you know maven, comment out the dependencies for this module(if not needed).
  
• b. When the maven build errors download it and install manually using the instructions at the end of the error message. A great post from Sergey is at: DAHDI Module Problems
• c. Not all of the ss7 modules are required for USSD. The dependencies for each module can be found in its pom. Just make sure you are able to cd into these directories and build them successfully. More-than-likely dahdi is not needed anyway. 

2. The build will error in test/simulator/pom.xml if the jmxtools cannot be found. This can be fixed by adding Ibrahims repo below to the primary pom repository list, so that it can find jmxtools, or install them manually.

                <repository>

                        <id>repo-for-missing-deps</id>

                        <name>TO FIX SOME MISSINGs</name>

                        <url>http://www.datanucleus.org/downloads/maven2/</url>

                </repository>

Hope this helps... Your doing better than I was when I started :)

v/r

James

[Ibrahima Gaye]

Hi James,

thanks for this valuable (at least for newbies like us) summary...

just to correct the jmxtolls part :) the repo is not mine, i donät even itäs from who loool

i just found it while digging online as usual Ö=

Warm regards,

------
Ibrahim

[James Carpenter]

Right, sorry that is what I meant. Just wanted to make sure they know who took the time to find it :)

Credit where credit's due, although poor wording. Anyway, carpe diem...

[Ibrahima Gaye]

oppps this was for here: 

... loool currently my lab ussdgateway is a mess i was trying to add sip client (like the http client already in) .... 

------
Ibrahim

On Thu, May 7, 2015 at 12:31 PM, James Carpenter <jfc...@gmail.com> wrote:

Right, sorry that is what I meant. Just wanted to make sure they know who took the time to find it :)

Credit where credit's due, although poor wording. Anyway, carpe diem...

--

[Mncedisi Kasper]

Hi James,

I'd already managed to compile the JSS7 stack, that's what I meant when I responsed to Ibrahim with the following message (extract)

-

The easiest way was to copy the 2.1.0-FINAL available jars from the JSS7 checked out here ( http://code.google.com/p/jss7/source/checkout), which I had already compiled.

-

The issue I have is compiling the ussggateway itself i.e. the one from here : http://code.google.com/p/jss7/source/checkout
When I try to change the pom in the ussdgateway to pull in 2.1.0-FINAL dependencies it fails, so a workaround I did was to
             1. copy the 2.1.0-FINAL dependencies generated when compiling JSS7 (which I had already compiled) manually to the mobicents-ussd-gateway/lib folder (and remove the older version of these depencencies)
             2. unpack the ussdhttpdemo.war, add the 2.1.0-FINAL versions of the map-api and map-impl dependencies, repack it
             3. verified that the versions of the dependencies in the simulator/lib folder are also the same as the ones on the deploy folder (which was not an issue since the simulator was compiled as part of JSS7 and therefore had the latest)

So at the moment my ussdgateway does have the 2.1.0-FINAL dependencies, but I'm recompiling it because I don't like the manual way I used to create it (plus I'm still having the MAPDialogState=EXPUNGED issue.

All that said though, I really appreciate the time you guys have spent, and are spending in helping me resolve this issue, truly amazing.

Regards

[James Carpenter]

Hi,

Ahh, I see. You are far past me. Good job!

There seems to be numerous similar posts on the forums related to this. It does seem to be a versioning issue as Sergey indicated in this post. Hope it helps.

[Mncedisi Kasper]

Yayyyyyyyyyyyy

Finally got it working, the problem was not the code version as I already had the latest 2.1.0.FINAL dependencies, the issue was that on the simulator I had "Route on GlobalTitle mode", the correct setting for my setup is "Route on DPC and SSN mode" and voila it works.

I've compiled a list of steps to compile JSS7, MAP RA, and the USSD Gateway using maven 3, will be publishing them soon. Hopefully it saves someone a week or three.

Regards

[Ibrahima Gaye]

​thanks for the feedback :)​

------
Ibrahim

--

[Ahmad Hammad]

hello freinds ,


can any one  please summries the steps , to install and abuild mobicent ussd gateway that full support sccp and sigtran ..
because i found that tis a common problem how make it run .


thanks all .




On Saturday, May 2, 2015 at 9:49:27 PM UTC+3, Mncedisi Kasper wrote:

Hi Guys,

Just spent two days trying to test my ussd gateway with no luck, some assistance would be appreciated. I've managed to compile and deploy successfully

When I run the simulator, however, I get a repeated log message as below, I however never get a response back from ussd gateway.

57948 [Thread-1] DEBUG org.mobicents.protocols.sctp.AssociationImpl  - Tx : Ass=Ass_main PayloadData [dataLength=164, complete=true, unordered=false, payloadProtocolId=3, streamNumber=2, data=
Start: 0 (0x00)  End: 163 (0xA3)  Length: 164 (0xA4)

57948 [Thread-1] DEBUG org.mobicents.protocols.sctp.AssociationImpl  - Rx : Ass=Ass_main PayloadData [dataLength=164, complete=true, unordered=false, payloadProtocolId=3, streamNumber=2, data=
Start: 0 (0x00)  End: 163 (0xA3)  Length: 164 (0xA4)

I would really appreciate some help, I've attached my config and server log.

Regards

[Mncedisi Kasper]

 Hi Ahmad.

I've been planning to publish them but real life has started intruding really badly, but I definitely agree with you this should definitely be tackled. I will be engaging with the guys in the coming weeks to see if they would be open to me helping out with updating documentation, etc.

I've attached a document that has the steps to compile the USSDGateway with Maven 3 and JSS7 2.1.0.FINAL dependencies, please check it out. I do believe though that I could get it to now work on maven 2, with the current dependencies on the project. The reason I got to compile with 2.1.0.FINAL JSS7 is because I thought there was a code issue and therefore tried to get the latest code, my actual issue though was configuration between the simulator and USSD GAteway so I'm planning on getting this to work as-is i.e. no changes to poms, etc. which will make the compile easier with very few changes.

In the meantime though, I've given options in the attached document 

1. Copy my working environment (jboss : https://s3.amazonaws.com/mtn-issues/jboss-5.1.0.GA.tgz, jboss : https://s3.amazonaws.com/mtn-issues/simulator.tgz) here and follow instructions in the docs to run them.

2. Follow the instructions to compile using maven 3, it requires quite a few changes to the poms but all of them are listed.

Please let me know if you run  into issues, I haven't gone though the steps since I captured them, but I captured all the steps as I was going along, so they should work.

Regards

 

[James Carpenter]

Hello,

I've posted my exact steps on a separate thread from a few days ago. If your interested you may utilize these to build from. I've also posted it here (my site for random notes).

v/r

James

[Sergey Vetyutnev]

Hello,

USSD GW is designed to be used not under JSS7 2.1.0.FINAL, but for some previous version.

I think that the idea of change Sbb's like this:
"Edit ChildSbb.java
vi core/slee/sbbs/src/main/java/org/mobicents/ussdgateway/slee/ChildSbb.java
– There are three instances of getLocalDialogId(). Change them to getDialogId()"

is not the best approach.

The problem why you need to try to update SBBs is because of you are using a wrong version of JSS7 stack / MAP RA. If you update only these SBBs in theory you can face with problems in another place.

I will try to create steps how to compile USSD GW "in a proper way".

[James Carpenter]

All I know is it works and I am using it :D

Can you provide any tips for the community on the "proper way" please? Any direction would help us learn. Or does the ussdgateway project just need updated for jss7 2.1.0.FINAL?

How can I see which version the ussdgateway is currently built for? I didn't alter the version from the git clone, just altered the LocalId function. I understand this could pose problems though.

v/r

James

--

You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

PGP Key Fingerprint:

798F FF6C 0E2F F63A FF70

D18B 378F DF44 EE74 0FDC

PGP Public Encryption Key available via

appropriate PGP Key Server distribution sites

Key ID: 0xEE740FDC

[Ibrahima Gaye]

From the main pom.xml : <ss7.version>2.0.0-SNAPSHOT</ss7.version>

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

[Sergey Vetyutnev]

Hello,

yes, USSD GW project needs to be updated if we wish to use JSS7 2.1.0

as for other questions I need no make some homework to create steps as I them see. Please wait.

[James Carpenter]

Hi Sergey,

Thank you for the explanation. If you can provide some direction as to how to integrate it properly, I can do my best to get it started. Is it just loading 2.1.0.FINAL and linking the new functions, changes?

Hi Ibrahim,

Right, my consolidated version is here. However, maybe I do not understand.

In the primary pom (https://code.google.com/p/ussdgateway/source/browse/pom.xml) it is listed as 2.0.0-SNAPSHOT. Is this the correct version for now? I did not download and deploy 2.1.0.FINAL only the MAP RA with jain-slee.ss7. I used your post from earlier regarding altering the LocalDialogId() function. Is this function not within 2.0.0-SNAPSHOT either? If so, what version  is the current ussd built for?

v/r

James

[Ibrahima Gaye]

Hi James,

in the main pom also the "required" map (jain-slee.ss7) is <mobicents.resources.map.version>2.0.0-SNAPSHOT</mobicents.resources.map.version> ...

i think the message from sergey is a big warning regarding mixing different version code;

laterly i added more changes.

Regards,

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

--

You received this message because you are subscribed to the Google Groups "mobicents-public" group.

[James Carpenter]

I see, thank you. Perhaps I am confused where the changes are being made.

Are you guys changing the google code and it is mirroring to GitHub? I haven't noticed any commits to compare files, versions with, etc.

Thanks again, I see what you are saying. I'll monitor my USSD instance for any irregularities.

v/r,

James

[Ibrahima Gaye]

Have you tested it with the simulator ?

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

--

[James Carpenter]

I've tested it with RestComm. (I think). It is connected and receiving the RestComm packets.

Been focused on smpp binding.

[Ibrahima Gaye]

​what protocol you used between restcomm and ussdgw ?

Regards,​

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

On Wed, May 27, 2015 at 6:20 PM, James Carpenter <jfc...@gmail.com> wrote:

I've tested it with RestComm. (I think). It is connected and receiving the RestComm packets.

Been focused on smpp binding.

--

[James Carpenter]

Wait, now that you got me thinking, I'm an idiot. You are right. I'm not using SIGTRAN, where MAP is necessary right?

That makes sense, although JBOSS says it is started, that doesn't mean it's working.

[Ibrahima Gaye]

take few hours of break and yoga :) ... after try again to make current public ussdgateway and restcomm interwork :)

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

On Wed, May 27, 2015 at 6:27 PM, James Carpenter <jfc...@gmail.com> wrote:

Wait, now that you got me thinking, I'm an idiot. You are right. I'm not using SIGTRAN, where MAP is necessary right?

That makes sense, although JBOSS says it is started, that doesn't mean it's working.

--

[James Carpenter]

Good idea actually, but got my coffee and SMPP.... I'll take a look at USSD some more when I start my TADHack brainstorming session :)

Thanks for the help.

[Ibrahima Gaye]

Good luck bro :)

​

------

Ibrahima GAYE,
Senior Project Management support
mob:

     +223  9  117 1464

     +221 77 564 9358 

My profiles:  Skype:ibgayel

www.tadhack.com 

If you received this email in error, please notify us immediately by sending an e-mail or by calling.

 

 

On Wed, May 27, 2015 at 6:48 PM, James Carpenter <jfc...@gmail.com> wrote:

Good idea actually, but got my coffee and SMPP.... I'll take a look at USSD some more when I start my TADHack brainstorming session :)

Thanks for the help.

--

[Mncedisi Kasper]

Hi James

As Sergey explains here , modifying the code to use getDialogId is not allowed, I had also started with that about two month ago here, Vilius then responded here to say it was not recommended, that's how I started down the road to using 2.1.0.FINAL because that version has getLocalDialogID. The thing I needed to investigate now on maven 2 was how to build without changing the code and also not using 2.1.0.FINAL. In my experience this will be tricky without mixing versions, ussd-gateway is built on 2.0.0-SNAPSHOT where the MapDialog api does not have getLocalDialogId.

The versions I've gotten to work so far are as follows
  - edited ussdgateway to use getDialogId ( Vilius did not recommend this approach, so I started using some 2.1.0.FINAL)
  - original ussdgateway with some 2.1.0.FINAL dependency to get it to compile with getLocalDialogId ( messages on ussdgateway were failing with status Expunged, I think this was more a config issue)
  - ussdgateway with 2.1.0.FINAL using maven 3, this is the working version I have  that has a simulator setup and connected (this is my current configuration, but as Sergey says here it's not built to use 2.1.0.FINAL)

At this point, I'll wait for Sergey to feedback on the best approach :-)

Regards

On Wednesday, May 27, 2015 at 5:00:46 PM UTC+2, James Carpenter wrote:

[James Carpenter, MISM MBA]

It still doesn't make sense. If that is the case, then there never was a working version of USSD with MAP RA. It makes more sense that the code has been edited since 2.0.0 or even 1.0.0, preventing a successful build. Hence, it needs reverted back to these settings to work, or update all of the dependencies.

Or wait for Sergey, as he seems to be owning the project att. I have to learn more Java lol in time :)

---

From: Mncedisi Kasper
Sent: ‎5/‎27/‎2015 8:57 PM
To: mobicent...@googlegroups.com
Subject: [mobicents-public] Re: testing ussd gateway

--

[Mncedisi Kasper]

Hi,

I think it might actually have worked before, I think what might have happened is that the version of 2.0.0-SNAPSHOT version of map-api and map-impl are different between what is committed to the public maven repos and the version the developers are using (take that with a pinch of salt or a handful :-)

From what I can see, MapDialog.getLocalDialogId() was added on December 2012 (version of pom is not changed), then there's a fix on the September 2013 to the ussdgateway slee that starts using getLocalDialogId(), which is actually the parts where the compilation as the MapDialog in 2.0.0-SNAPSHOT does not contain getLocalDialogId() which explains the error we're getting. This of course leads to my suspicion that that map-api, and map-impl 2.0.0-SNAPSHOT was not updated in public repos.

Anyway all speculation until Sergey comes back.

Regards