Git Product home page Git Product logo

jss7's People

Contributors

abhayani avatar baranowb avatar lasithwaruna avatar normandesjr avatar oifayulian avatar vetss avatar vinusaseedaran avatar

Watchers

 avatar

jss7's Issues

Max sequence number should be configurable in SCTP

As of now max sequence number is hardcoded to 32. If SCTP user sends 
PayloadData with stream number greater than 32, it truncates it to zero which 
is wrong.

Max sequence number should be configurable and if PayloadData with stream 
number greater than max sequence number is received, it should drop the packet 
and log errors.

Original issue reported on code.google.com by [email protected] on 18 Apr 2012 at 9:31

Revise MAP API

History : http://code.google.com/p/mobicents/issues/detail?id=2891

Original issue reported on code.google.com by [email protected] on 15 Apr 2012 at 10:49

java.util.EmptyStackException when TCAP Dialogs are all utilised

When all TCAP Dialog's are utilized, it throws below error

Caused by: java.util.EmptyStackException
    at java.util.Stack.peek(Stack.java:102)
    at java.util.Stack.pop(Stack.java:84)
    at org.mobicents.protocols.ss7.tcap.DialogIdIndex.pop(DialogIdIndex.java:36)
    at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.getAvailableTxId(TCAPProviderImpl.java:145)
    at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.getNewDialog(TCAPProviderImpl.java:198)
    at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.getNewDialog(TCAPProviderImpl.java:193)
    at org.mobicents.protocols.ss7.map.MAPServiceBaseImpl.createNewTCAPDialog(MAPServiceBaseImpl.java:86)
    at org.mobicents.protocols.ss7.map.service.sms.MAPServiceSmsImpl.createNewDialog(MAPServiceSmsImpl.java:84)
    at org.mobicents.slee.resource.map.wrappers.MAPServiceSmsWrapper.createNewDialog(MAPServiceSmsWrapper.java:119)


Rather it should throw meaningful exception like
"Can't create more TCAP Dialogs. Exceeding max concurrent TCAP Dialog's allowed 
XXXX" 

Original issue reported on code.google.com by [email protected] on 19 Apr 2012 at 9:21

SSN ==0 should not be considered while making translation check for primary/secondary SCCPAddress

As of now, the SSN from primary/secondary address is checked if its SCCP 
Management SSN (SSN==1) or if its not, whether the SCCPListener is registered 
for this SSN; if both above condition fails it returns 
TranslationAddressCheckingResult.destinationUnavailable_SubsystemFailure.

However SSN of primary/secondary address can be 0 indicating that SSN received 
from called SccpAddress is to be used in translated SccpAddress.

Original issue reported on code.google.com by [email protected] on 15 Apr 2012 at 11:30

SCCP Rule should follow best matching approach

As of SCCP rule takes first matching rule rather than best matched rule.

For example consider Rule1 defined with GT digits * and Rule2 defined with GT 
digits 1234. If SccpAddress to be compared has digits 1234, routing control 
will still return Rule1 instead of Rule2 as Rule1 is defined before Rule.  


Original issue reported on code.google.com by [email protected] on 15 Apr 2012 at 11:26

Bring back support for dahdi based cards (Diguim, Sangoma)

Mobicents SS7 supported dahdi based cards Diguim and Sangoma, however due to 
performance degrading at high load, the module was removed from binary release 
(while still available in source code).

Update the code to improve performance and include in binaries


Original issue reported on code.google.com by [email protected] on 17 Apr 2012 at 1:36

SCTP sequence id not respected for incoming packet

When SCTP packet is received from far end (specifically start of TCAP - 
Dialog), its possible that SLS value is different from SCTP Sequence ID, 
however the response to this packet sent out always uses SLS as SCTP Sequence 
ID. This causes far end to send back "Invalid Stream Identifier" Error.


Original issue reported on code.google.com by [email protected] on 24 Apr 2012 at 10:29

Typo when adding Associoation in response

What steps will reproduce the problem?
1.When adding association through ss7-run.sh

What is the expected output? What do you see instead?
12:00:55,709 INFO  [ManagementImpl] Added Associoation=STPB of type=CLIENT


What version of the product are you using? On what operating system?
2.7.0-snapshot

Please provide any additional information below.
Is there any way to mark these as trivial changes and not bugs? 

Original issue reported on code.google.com by [email protected] on 5 May 2012 at 7:04

NPE while reading SCCP Rule from persist file

Create Rule without passing the LoadSharingAlgorithm in which case it should 
persist "Undefined" as default. However the xml file doesn't have this value 
and hence while reading it back gets NPE


16:30:12,718 INFO  [Router] SCCP Router configuration file path 
/home/abhayani/workarea/mobicents/binary/JSLEE/smsc-mobicents-jainslee-2.6.0.FIN
AL-jboss-5.1.0.GA/jboss-5.1.0.GA/server/default/data/SccpStack_sccprouter.xml
16:30:12,722 ERROR [AbstractKernelController] Error installing to Start: 
name=SccpStack state=Create
java.lang.NullPointerException
    at org.mobicents.protocols.ss7.sccp.impl.router.Rule$1.read(Rule.java:401)
    at org.mobicents.protocols.ss7.sccp.impl.router.Rule$1.read(Rule.java:397)
    at javolution.xml.XMLFormat$InputElement.readInstanceOf(XMLFormat.java:467)
    at javolution.xml.XMLFormat$InputElement.get(XMLFormat.java:363)
    at javolution.xml.XMLBinding$3.read(XMLBinding.java:400)
    at javolution.xml.XMLFormat$InputElement.readInstanceOf(XMLFormat.java:467)
    at javolution.xml.XMLFormat$InputElement.get(XMLFormat.java:410)
    at javolution.xml.XMLObjectReader.read(XMLObjectReader.java:277)
    at org.mobicents.protocols.ss7.sccp.impl.router.Router.load(Router.java:516)
    at org.mobicents.protocols.ss7.sccp.impl.router.Router.start(Router.java:239)
    at org.mobicents.protocols.ss7.sccp.impl.SccpStackImpl.start(SccpStackImpl.java:314)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)



Original issue reported on code.google.com by [email protected] on 16 Apr 2012 at 3:39

SCTP Association needs of supply its connection status

Now there is no way of determing if the SCTP/TCP connection is up or down 
(connected or disconnected). 
"public boolean Association.isConnected();" method is suggested for its purpose.

Also a bug in sctp project is fixed - sctp Association did not try to reconnect 
if Exception occured when connection initiating (for example when "Address in 
use" error).

Original issue reported on code.google.com by [email protected] on 17 Apr 2012 at 7:35

Attachments:

SCTP shouldn't maintain the sequenceNumber

SCTP library shouldn't maintain the sequence identifier table. Rather it should 
call back the AssociationListener if SCTP users sends payload with sequence 
greater than maxOutboundStreams of underlying (sctp)Socket and drop packet.


Original issue reported on code.google.com by [email protected] on 19 Apr 2012 at 3:36

TCAP stack always overrides invoke timeout

What steps will reproduce the problem?
1. Setup a tcap transaction with a custom timeout
2. Send the invoke
3. DialogImpl replaces custom timeouts with stack configured value:

            invoke.setState(OperationState.Pending);
            invoke.setDialog(this);
            invoke.setTimeout(this.provider.getStack().getInvokeTimeout());
So no matter what has been set in invoke before sending - it is beeing replaces 
with a value configured for the stack.


What is the expected output? What do you see instead?
it should be possible to ]
Temporary solution is to set stack timeout to 0 - so no timeouts are generated

What version of the product are you using? On what operating system?
SS7 2.0.0Beta trunk

Please provide any additional information below.
The quick solution might be allowing to set up invoke timeout only once - in 
the InvokeImpl.java

Original issue reported on code.google.com by [email protected] on 19 Apr 2012 at 11:06

Expose TCAP stack for configuration in mobicents-ss7-service

As of now SCCP Provider is bound to JNDI and MAP RA creates TCAP, MAP stack. 
this causes many configuration nightmare.

Better to expose TCAP and MAP stack as beans in jboss-beans.xml of 
mobicents-ss7-service and let MAP RA do the lookup of MAPProvider directly.


Original issue reported on code.google.com by [email protected] on 23 Apr 2012 at 9:39

CLI help screen, TAB Completion feature

As of now all the management commands entered at client side are passed to 
server side without any validation for variable.

Add the validation and show appropriate error message on Shell CLI.

Implement the help for Shell CLI.

May be leverage http://jline.sourceforge.net/ for maintaining history and auto 
completion of commands?


Original issue reported on code.google.com by [email protected] on 15 Apr 2012 at 10:44

TCAP stack core update: TC-Notice support

As for now the support of TC-Notice indication at TCAP level is not implemented.

We are:
- adding: TCListener.onTCNotice(TCNoticeIndication ind);
- removing: TCBeginRequest(and other requests).setQOS(Byte b) throws 
IllegalArgumentException;
- adding TCBeginRequest(and other requests).setReturnMessageOnError(boolean 
val); - default value is false - if this option is up TCAP will ask SCCP to 
return message if it can not be delivered. If the message has not been 
delivered setReturnMessageOnError() will be invoked
- adding setReturnMessageOnError(boolean val) to the MAP/CAP Stack and Dialogs 
so MAP/CAP users can control this behaviour

Original issue reported on code.google.com by [email protected] on 30 Apr 2012 at 5:30

MAPParsingComponentException: IOException when decoding MAPUserAbortInfo: AsnInputStream has reached the end

When parsing the MAPUserAbortInfo get the below error

2012-05-07 14:51:56,969 ERROR [org.mobicents.protocols.ss7.map.MAPProviderImpl] 
When parsing TCUserAbortIndication indication: 
MAPParsingComponentExceptionIOException when decoding MAPUserAbortInfo: 
AsnInputStream has reached the end
org.mobicents.protocols.ss7.map.api.MAPParsingComponentException: IOException 
when decoding MAPUserAbortInfo: AsnInputStream has reached the end
    at org.mobicents.protocols.ss7.map.dialog.MAPUserAbortInfoImpl.decodeAll(MAPUserAbortInfoImpl.java:103)
    at org.mobicents.protocols.ss7.map.MAPProviderImpl.onTCUserAbort(MAPProviderImpl.java:1075)
    at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.deliver(TCAPProviderImpl.java:319)
    at org.mobicents.protocols.ss7.tcap.DialogImpl.processAbort(DialogImpl.java:1406)
    at org.mobicents.protocols.ss7.tcap.TCAPProviderImpl.onMessage(TCAPProviderImpl.java:608)
    at org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl.route(SccpRoutingControl.java:449)
    at org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl.translationFunction(SccpRoutingControl.java:383)
    at org.mobicents.protocols.ss7.sccp.impl.SccpRoutingControl.routeMssgFromMtp(SccpRoutingControl.java:145)
    at org.mobicents.protocols.ss7.sccp.impl.SccpStackImpl.onMtp3TransferMessage(SccpStackImpl.java:736)
    at org.mobicents.protocols.ss7.mtp.Mtp3UserPartBaseImpl$MsgTransferDeliveryHandler.run(Mtp3UserPartBaseImpl.java:181)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)
Caused by: java.io.EOFException: AsnInputStream has reached the end
    at org.mobicents.protocols.asn.AsnInputStream.read(AsnInputStream.java:176)
    at org.mobicents.protocols.asn.AsnInputStream.readLength(AsnInputStream.java:288)
    at org.mobicents.protocols.asn.AsnInputStream.readNull(AsnInputStream.java:880)
    at org.mobicents.protocols.ss7.map.dialog.MAPUserAbortInfoImpl._decode(MAPUserAbortInfoImpl.java:170)
    at org.mobicents.protocols.ss7.map.dialog.MAPUserAbortInfoImpl.decodeAll(MAPUserAbortInfoImpl.java:101)
    ... 12 more

Original issue reported on code.google.com by [email protected] on 8 May 2012 at 7:39

TCAP stack core update: unproper message processing details

As for now when processing incoming TCAP messages provider errors are not 
processing correctly. We need to announce both of the local TCAP user and the 
remote peer.

To achieve this I have added TCPAbortIndication.isLocalProviderOriginated().
TCListener.onTCPAbort(TCPAbortIndication ind) will be delivered to both of the 
local and remote peer.

Original issue reported on code.google.com by [email protected] on 28 Apr 2012 at 5:11

SCCP doesn't respect point-code for incoming message

Suppose SCCP stack is configured with multiple rsp and SCCP Rule1 configured to 
use PC1 as primary and PC2 as secondary. Now if message received from PC2 and 
consumed by SCCP-User and replies back, the GT matches for Rule1, it will use 
PC1 for out going message instead of PC2.

Original issue reported on code.google.com by [email protected] on 15 Apr 2012 at 6:15

SS7 manual update

SS7 manual needs to be updated to the new (2.0) release and become more 
comfortable.
Corresponded examples should be updated

Original issue reported on code.google.com by [email protected] on 11 May 2012 at 1:13

bad tp-service-centre-time-stamp

What steps will reproduce the problem?
1. Send an MT-ForwardSM
2. Take a PCAP trace
3. Timestamp is wrong, showing an older tade

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 3 May 2012 at 2:40

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.