Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Without 'lowercase field':
- ERSCS582141 not found
- With 'lowercase field':
- ERSCS582141 found at position 1
- The query:
- TCTDI gives NOT ACCEPTED 3 for R1 values
- TCTDI is not accepted for UPDDIV
- The document:
- ubuntu@ml-server:~/machinelearning/metis/input_solr$ cat input_files_json_2/ERSCS582141.json
- {'id': 'ERSCS582141', 'title': ' tctdi gives not accepted 3 for some r1 values ', 'description': "ac nwbzt-0221(wrong gsn connection state sent in pfnrr1) in block upddiv before correction loading when a route for dety=upddiv is defined, upddiv sends s' pfnrr1 with d3=1 (connection to gsn), without checking the gsnttype, which for the case of upddiv has the value 1 (devices gs connected). after the correction loading upd will check gsnttype before sending of pfnrr1 and set d3 and also d5 properly for each gsnttype which for the case of upddiv has the value 0 (devices not gs connected). this results in rtype in block ra being set to 1=software route instead of 2=trunk route. routes of type 1 can not be used for tctdi. ether this has to be set back to the old way or a new way of seeing if the route can be used for tctdi r1. a similar to what happened for tctdi on dev in correction n01zt-0225 replaced by n01he-0975.see tr hh26395 tctdi fails with upddiv route in r1 parameter for routes created after ac nwbzt-0221 was loaded tctdi gives not accepted 3 for some r1 values tctdi fails if r1 (model route) is not gs-connected tctdi fails if r1 is a sip, h.323 or bicc route. ", 'reuseCount': 7}ubuntu@ml-server:~/machinelearning/metis/input_solr$
Advertisement
Add Comment
Please, Sign In to add comment