Closed GoogleCodeExporter closed 9 years ago
Here is a first update for CAP tests supporting in Simulator:
http://code.google.com/p/jss7/source/detail?r=a24792699a6ce245e562cab8af233e0599
7da3d8
http://code.google.com/p/jss7/source/detail?r=c52adda48f1229ee2b332b191a5ae93bf0
c7fd57
http://code.google.com/p/jss7/source/detail?r=6992cfb38ef2290ff7e15a207448e748b7
bc0154
Not all is implemented. This part is for first testing only.
Original comment by serg.vet...@gmail.com
on 26 Jan 2013 at 12:23
Next updates:
http://code.google.com/p/jss7/source/detail?r=d784c859ce3f580d6f2a537a10d6a3e4ec
08929f
http://code.google.com/p/jss7/source/detail?r=892f68017ceaa7e943c4c0d442b1defc08
accd46
Now GsmSSF side can:
- open a new Dialog and send InitialDp component
- open a new Dialog and send AssistRequestInstructions component
- send ApplyChargingReport component within a current Dialog
- send EventReportBCSM component within a current Dialog
- close a current Dialog with empty TC-END message
GsmSCF side can:
- send ApplyCharging component within a current Dialog
- send Cancel component within a current Dialog
- send Connect component within a current Dialog
- send Continue component within a current Dialog
- send ReleaseCall component within a current Dialog
- send RequestReportBCSMEvent component within a current Dialog
- close a current Dialog with empty TC-END message
Now all operations are sent with a set of predefined parameters and Simulator
user can not specify parameters values. This is a further task.
Only one opened dialog at the same time is supported by Simulator
Original comment by serg.vet...@gmail.com
on 7 Feb 2013 at 4:10
I am marking this issue as fixed.
I have created a new issue for adding configurable parameters into Simulator :
https://code.google.com/p/jss7/issues/detail?id=271
Original comment by serg.vet...@gmail.com
on 18 Apr 2013 at 7:34
Original comment by serg.vet...@gmail.com
on 18 Apr 2013 at 7:35
Original comment by amit.bha...@gmail.com
on 3 Nov 2013 at 12:10
Original comment by amit.bha...@gmail.com
on 3 Nov 2013 at 12:15
Original issue reported on code.google.com by
serg.vet...@gmail.com
on 18 Jan 2013 at 11:37