Page 1 of 1

OverflowType values

Posted: 02 Dec 2018 12:08
by ssteiner
Why does OverflowType have 3 different values? The way I understand it, forwardroutes always come first. So, the only relevant usages of overflows are if there's no forward (or a busy forward), then the overflow route can come into play, and it will always be of type NO_ANSWER. The other two values, I've only seen them in an OTMS scenario on CV users.
Am I missing something or is this another thing that wasn't cleaned up when rewriting the documentation from OTMS to O2G?

Re: OverflowType values

Posted: 03 Dec 2018 10:44
by yblanchard
Not exactly: the API allows to register a forward on non response to Alice and in the same time to register an overflow on busy on Bob (which may be the associate or not).
I agree that you can do the opposite (forward busy on bob and ovf non response on Alice, it will have the same result), but if we consider that ovf is generally on associate...

Re: OverflowType values

Posted: 04 Dec 2018 09:27
by ssteiner
So, that overflow on busy you speak of, would that be the "Overfl.busy to assoc. set" in the dynamic user state?

Re: OverflowType values

Posted: 05 Dec 2018 08:45
by yblanchard
exactly