Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USSD PUSH configuration issues with SS7-SIM #93

Open
armachea opened this issue Jul 10, 2018 · 13 comments
Open

USSD PUSH configuration issues with SS7-SIM #93

armachea opened this issue Jul 10, 2018 · 13 comments

Comments

@armachea
Copy link

What happened:

Hi guys, hope everyone is having a great day so far. I have restcomm-ussd-7.1.0-SNAPSHOT--wildfly-10.1.0.Final installed on Ubuntu [16.04] I have tested all scenarios but when it comes to ussd push am getting an error about local SSN.

PostMan
>>>> USSD GW
>>>> SS7-SIM
What you expected to happen:

Well I am pretty sure, my SS7-SIM should receive more than the SRI req/resp. It supposed to received the string message from the xml payload. But i can't receive the message.

How to reproduce it (as minimally and precisely as possible):
This is what i get from USSD GW after firing Postman payload.
WARN FROM USSD GW:
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
13:01:25,404 WARN [org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl] (pool-5-thread-1) Received SccpMessage=Sccp Msg [Type=UDT networkId=0 sls=6 incomingOpc=2 incomingDpc=1 outgoingDpc=-1 CallingAddress(pc=2,ssn=6,AI=83,gt=GlobalTitle0100Impl [digits=000, natureOfAddress=INTERNATIONAL, numberingPlan=ISDN_TELEPHONY, translationType=0, encodingScheme=BCDOddEncodingScheme[type=BCD_ODD, code=1]]) CalledParty(pc=0,ssn=8,AI=18,gt=GlobalTitle0100Impl [digits=923330053058, natureOfAddress=INTERNATIONAL, numberingPlan=ISDN_TELEPHONY, translationType=0, encodingScheme=BCDEvenEncodingScheme[type=BCD_EVEN, code=2]]) DataLen=77] for Translation but no local SSN is present for primary Address
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Anything else we need to know?:

PostMan is running on : 192.168.43.12
USSD-GW is running on: 192.168.43.13
SS7-SIM is runnin on: 192.168.43.14
I have restcomm-ussd-7.1.0-SNAPSHOT running on wildfly 10.1.0

@nhanth87
Copy link
Contributor

I think you already change the SSN number to another number (example 147) instead of 8?

Br,
TN

@armachea
Copy link
Author

Yes, That's correct i tried with 147 and 8 for local SSN........ unfortunately, i got the same WARN for both case.

nhanth87, is there a thing am missing? I am totally out of solution.

@nhanth87
Copy link
Contributor

Cna you send me data *.xml file?

@armachea
Copy link
Author

Sure thing, this is the .xml files for ussd-gw.
xmlFILES.zip

@armachea
Copy link
Author

Guys, any advice regarding this problem.......

@nhanth87
Copy link
Contributor

Hi,
In the standalone.xml, please add extra ssns = 8 and try again

        <mbean class="org.mobicents.protocols.ss7.tcap.TCAPStackImpl" enabled="true" name="TcapStack" reflection="false" type="TcapStack">
            <property name="sccpStack" type="Bean" value="SccpStack"/>
            <property name="ssn" type="int" value="147"/>
            <property name="previewMode" type="bool" value="false"/>
            **<property name="extraSsns" type="Map" value="empty">
                <entry key="1" type="int" value="6"/>
            </property>**
        </mbean>

@armachea
Copy link
Author

Hi nhanth87,

I just wanna thank you for the time and guidance you giving me, I have added the above config but something is off. am receiving a warning that i am sending a ussd push FROM PC=0 TO PC=0. This is crazy, because i have updated the routing address in standalone.xml and SccpStack_sccprouter2.xml in USSD GW.

||||||||||||| USSD PUSH INSIDE POSTMAN ||||||||||||||||

||||||||||||| UPDATED STANDALONE.XML USSD GW ||||||||||||||||







||||||||||||| UPDATED SccpStack_sccprouter2.xml USSD GW ||||||||||||||||











????? Not to forget that i have update the imsi number with random digit from ss7-sim side because without the imsi number was receiving an error regarding [TypeMismatch]......... All of the changes i have done is leading me to | ussd push FROM PC=0 TO PC=0 | with ss7-sim only receiving SRI req/res.

This is the WARN

13:22:15,750 WARN [org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl] (SLEE-EventRouterExecutor-3-thread-1) Received SccpMessage for Translation but no matching Rule found for local routing
SccpMessage=Sccp Msg [Type=-1 networkId=0 sls=2 incomingOpc=-1 incomingDpc=-1 outgoingDpc=-1
CallingAddress(pc=0,ssn=8,AI=18,gt=GlobalTitle0100Impl [digits=923330053058, natureOfAddress=INTERNATIONAL,numberingPlan=ISDN_TELEPHONY, translationType=0, encodingScheme=BCDEvenEncodingScheme[type=BCD_EVEN, code=2]])
CalledParty(pc=0,ssn=8,AI=18,gt=GlobalTitle0100Impl [digits=, natureOfAddress=INTERNATIONAL, numberingPlan=ISDN_TELEPHONY, translationType=0, encodingScheme=BCDEvenEncodingScheme[type=BCD_EVEN, code=2]]) DataLen=178]

@armachea
Copy link
Author

updated sccpstack_sccprouter2 xml ussd gw
updated standalone xml ussd gw
ussd push from postman

@nhanth87
Copy link
Contributor

The log looks good,
We now pass the issue no local SSN is present for primary Address and it's come to no matching Rule found for local routing

You need to look into the called party for the routing rule.

@nhanth87
Copy link
Contributor

can you send full server.log, need to check it's SRIforSM or USS_Notify message?

@armachea
Copy link
Author

It's definitely a SRIforSM....

Please this is the full server.
server.log
log

@armachea
Copy link
Author

Hi nhanth87,

Hope you doing fine.... I was wondering if there is any changes needed from the SS7-SIM ? in order to make this work.

Regards

@armachea
Copy link
Author

armachea commented Aug 6, 2018

Hi guys Anybody here ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants