Some FAQs on UIM Telephone Number Portability
(Doc ID 1483280.1)
Last updated on AUGUST 13, 2019
Applies to:Oracle Communications Unified Inventory Management - Version 7.2.0 and later
Information in this document applies to any platform.
Checked for relevance on 03-Oct-2014
Some Queries regarding usage of Number Portability functionalities available in UIM.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Questions and Answers|
|Q1. When UIM picks up value from tnType = PortedOut and change TN Assignment state to Ported?|
Q2. Looking for more documentation on UIM_HOME/config/consumer.properties. Some of these parameters are self-explanatory but some of them not.
Q3. What is purpose of using winback parameter in Base Phone management cartridge. As its understand this characteristic as it is used when the number is returning back from PortedOut state.
Q4. Wanted to know Life Cycle Management for using Porting OOB functionality. What are available transitions?
Q5. Is there any automation behind these two attributes- PortedIn, Owned? Like in case of PortOut?
Q6. Winback is used when customer comes back to the same provider with the same TN as he ported out before? If some this attribute is complementary to Snapback functionality, isn't it? Such as it should be checked by snapback as well.
Q7. PortIn is used when customer comes to you with TN from different provider, isn't it? If so this TN will never ever be TNtype = Own?
Q8. It means that if TN type is empty the TN has no aging process? If not I'm sorry but I can not see the relationship between TN type and TN aging process.
Q9. So Winback usage is based on local convention based on regulatory?
Q10. You have a POOLING process and you have implemented UIM rule for it. And I understand the relation ship between pooling and PortIn value.
Q11. What about TOLLFREE? There is any TN aging related changes?