Status: Accepted
Owner: [email protected]
CC: [email protected], [email protected], [email protected]
Labels: Type-Enhancement Priority-Medium Component-SS7 Roadmap-Fix
Version-2.1.0.BETA1
New issue 264 by [email protected]: Add support for empty TC-BEGIN
scenario into SS7-Simulator
http://code.google.com/p/jss7/issues/detail?id=264
For SMSC testing we need to support by Simulator a scenario:
- if the length of short message (in bytes) is little less than max
possible (max possible=140 bytes) (120-140 depending on other parameters)
it is impossible to carry MoForwardSM request Invoke with Dialog part in
one TC-BEGIN TCAP message because of big summarized size.
- to overcome it the following scenario is used:
- -> TC-BEGIN message with only Dialog part
- <- empty TC-CONTINUE message
- -> TC-CONTINUE message with MoForwardSM request
- <- TC-END with MoForwardSM response
We need to implement this scenario in Simulator for SMSC testing.
If encoded SmsSignalInfo is >= 110 bytes and MAP version>1 we will use this
scenario.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
