No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-CLF didn't refresh the its Option82 record in real time even new DHCP request have be sent by the SIP terminal which having different Option82 than previous

Publication Date:  2012-08-06 Views:  51 Downloads:  0
Issue Description

Q:
The AIM version used is V100R005C02 and the CSCF version is V100R006C02. 
During implementing NASS-Bundle Authentication, the SIP UE still able to register successfully even using anothers port (FTTH or IP MSAN), which having different Option82 info. 
By right, the UE can only register successfully to IMS with the right port which having the correct Option82 info. 

Alarm Information

None


Handling Process
A:
After check on the AIM configuration, found 2 mistake configuration
1)The NACF Realm Mapping's domain name didn't match with the CLF configuration which cause the bind fail. Execute below to revise.
MOD NRMAP:NID=0,RID=0,REALM="vobb.ims.tm.com.my",LGID=10,PHYID=10,CHN="rcclfhw01.ims.tm.com.my";
2) In ADD NIPPI,the parameter NACK=ACK change to NACK. If select ACK, it means end user can allocate with an IP even the bind fail. If select NACK, 
end User only can obtain an IP once bind success. Execute below to revise.
MOD NIPPI:NID=0,PLID=1, BINDEN=ALL_ENABLE, WTEN=YES, NACK=NACK;
Root Cause
According to the trace capture on register flow, notify when PCSCF query the CLF (UDR) and CLF reply the UDA carry with the previous Option82 info, 
which is match with the HSS subscriber data. That's why the register still success.  
Through MML command, DSP GUAI on AIM show the UE Option82 information. Check the DHCP DISCOVERY message which bring the new option82 and found 
that there are different. It shows CLF still maintain the previous Option82 infomation and didn't update the latest Option82 Infomation during DHCP Request.
Suggestions
Always precaution on the domain name that define on PCSCF, RM and AIM, such as those configuration like PACN, SROUTE, NIPPI, NRMAP,
CRMAP to avoid leading malfunction.

END