Comment #9 on issue 205 by [email protected]: CAP - Implement initialDPGPRS CAP V3 Operation
http://code.google.com/p/jss7/issues/detail?id=205

Hello!

About the last patch:

1. SendChargingInformationGPRSRequest
It looks like the encdoding is still wrong:
From your test:
48, 44,
  -96, 42,
-96, 37, -96, 21, -128, 1, 1, -127, 1, 2, -126, 1, 3, -125, 1, 4, -124, 1, 5, -123, 1, 6, -122, 1, 7, -95, 12, -96, 6, -125, 1, 4, -124, 1, 5, -127, 2, 0, -34,
    -127, 1, 1

I think it should be:
48, <length>, SEQUENCE - SendChargingInformationGPRSArg {PARAMETERS-BOUND: bound}::= SEQUENCE { 128, <length>, [0] - primitive (OCTET STRING) - SCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE (4 .. 255)) 48, <length> - CAMEL-SCIGPRSBillingChargingCharacteristics ::= SEQUENCE {
      160, <length>, <element> - aOCGPRS [0] AOCGPRS
      129, <length>, <element> - pDPID [1] PDPID OPTIONAL

2. CAPFunctionalTests: I have not checked details. You can check MAP and CAP functional tests now by creating a test trace pcap file and checking it then by WireShark.
To do this please follow these steps:
- select one test for testing, for example we starts with testGPRS1()
- insert at the beginning of the test code (for example before "long stamp = System.currentTimeMillis();") this code:
"this.saveTrafficInFile();"
- run the test for example in Eclipse
- then you can find a new file "MsgLog.pcap" in "cap" folder
- open it by WireShark and check if it "understands" all correctly
- remove or comment "this.saveTrafficInFile();" line

then you can move to a next gprs test.

Please commit your update. Pay attention that it will be conflicts in initialDPGprs merging because of this my update:
http://code.google.com/p/jss7/source/detail?r=b35cb0b7edbebd38ba4653b686cc576ff7b185cd





--

--- 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.


Reply via email to