To analyze this case, first we should clear understanding that ATS is the only ME which generate the Charging ACR to CCF for recoding the CDR. First action taken is to capture the signaling trace by getting the affect the User and generate outgoing call. Signaling trace has been setup to capture on ATS. On the trace, the 1st incoming invite do carry the P-Access-Network Info correctly, which indicates the End user do provide the information correctly to the Server. As show below:
Secondly, we analyze the Diameter Message. (ACR which is use for charging purpose and interacting with CCF). P-Access-Network Info will be one of the AVP (Added Value Parameter) forward to CCF. And found that in the ACR message, ATS only forward XDSL without the details location information.
Compare to normal Scenario, the ACR message should as following:
Compare these 2 location information we found that the length is different.
xDSL;dsl-location="0 0/0/0:4096.400 SBJ_G05/1/1/5/0/2/FHTT-0024829c GP";"location-info=0 0/0/0:4096.400 SBJ_G05/1/1/5/0/2/FHTT-0024829c GP" =(140 characters) not ok
XDSL;dsl-location="0 0/0/0:4096.400 MTM_V1014/1/1/3/0/4:0.400";"location-info=0 0/0/0:4096.400 MTM_V1014/1/1/3/0/4:0.400" =(120 characters) ok