SSRV JMS CDR
The SSRV-JMS generates CDRs which are stored in tango/data/cdr/ssrv-jms.cdr
. The following apply:
-
Successful
-
Intermediate timeout
-
Final failed timeout
-
Intermediate error code
-
Final failed error code
All options are written in the same format as shown in the associated table. Check out the samples for each format in SSRV JMS CDR Samples. |
Field | Name | Description | ||
---|---|---|---|---|
1 |
|
The MSISDN of the subscriber. |
||
2 |
|
The service type which is 17 in this case. |
||
3 |
|
The transaction type which is 19 for JMS. |
||
4 |
|
The date on which the CDR was generated. Format: |
||
5 |
|
The time at which the CDR was generated. Format: |
||
6 |
|
The call reference from the SE request such as |
||
7 |
|
The service respone code for example 70. |
||
8 |
|
The message associated with the service response such as Failed to connect or something along those lines. |
||
9 |
|
The time at which the JMS request was submitted. Format: |
||
10 |
|
The time at which the JMS response was received. Format: |
||
11 |
|
The processing time delay (latency) in milliseconds. |
||
12 |
|
If custom CDR data has been configured via the Tango GUI, it appears here.
|
SSRV JMS CDR Samples
Successful CDR
0004100102030405,17,19,2015/08/13,11:41:20,MyCallRef,0,Successfull,11:41:12,11:41:20,8387,{}
Intermediate Timeout CDR
0004100102030405,17,19,2015/08/13,11:45:40,MyCallRef,71,JMS request(0 of 2 retries) failed with timeout,11:45:32,11:45:40,8387,{}
Final Failed Timeout CDR
0004100102030405,17,19,2015/08/13,11:46:02,MyCallRef,70,Failed to connect to JMS Service,11:45:32,11:46:02,30723,{}