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

The number is not in the global format causes ATS restricted the incoming call incorrectly

Publication Date:  2012-08-06 Views:  104 Downloads:  0
Issue Description
ats version is v100r003c00. cancel the ims subscriber’s international incoming call right on ats, then make a national call from pstn to this subscriber, but the call is been restricted.
Alarm Information
Null
Handling Process
from the ats interface message we can see the caller number which sent to ats is not a global number (format is: +CC+NC+SN), this is number does not contains the country code.


the principle of ats analyzing the call attribute is:
1. get the called number's country code (by querying the called number's local dn set table), use this country code to match the caller number's prefix, if matched, then this is a national call, otherwise is an international call.

2. if ats take this call as national call by step 1, then it will use the called number's national code (also by querying the called number's local dn set table) to match the caller number's rest digits, if matched, then this is a local call, otherwise this is a national call.

3. if the caller number is mobile number (defined by add mblpfx) then ats will take this call attribute as unknown because at the mt side ats can not distinguish this call is local call or national call, so ats will not check the incoming call right for this kind calls.

in this case the caller number is 02066853641, and the called number's country code is 86, they are inconsistent, so ats take this call as international call and restrict it. the root cause is that the number which sent to ats does not meet the number format specifications, in ims domain the number should be in the global number format. after changing the ugc's configuration to make it send the global number to ims domain, the problem is been solved.
Root Cause
the call barring is processed on ats. for the incoming call restriction ats will use the caller number’s address nature (NOA) to match the called number’s incoming call right, if matched then ats will restrict the call. in this case we only canceled the caller number’s international incoming call right, not include the national incoming call right, so there may be the ats made a mistake about analyzing the caller number's NOA.
Suggestions
the principle of ats analyzing the call attribute is:
1. get the called number's country code (by querying the called number's local dn set table), use this country code to match the caller number's prefix, if matched, then this is a national call, otherwise is an international call.

2. if ats take this call as national call by step 1, then it will use the called number's national code (also by querying the called number's local dn set table) to match the caller number's rest digits, if matched, then this is a local call, otherwise this is a national call.

3. if the caller number is mobile number (defined by add mblpfx) then ats will take this call attribute as unknown because at the mt side ats can not distinguish this call is local call or national call, so ats will not check the incoming call right for this kind calls.

END