ASAI and Call Control
■The originator is a hunt group with no available AWOH members (cause=CS0/17).
■The originator is busy on one call appearance in talking state (cause=CS0/17).
■The originator has “hot line” administered (cause=CS0/58).
■The call could not be originated because of lack of resources (cause=CS3/40).
■A UUI Information Element longer than 32 bytes was received (cause=CS0/100).
■The originator is not a valid station extension (cause=CS0/28).
■A service circuit is requested (cause=CS3/80).
■Answering Machine Detection is requested (cause=CS3/80).
A call placed to a called endpoint whose COR does not allow the call to end will return intercept treatment to the calling endpoint and the Reorder event with cause CS0/21 (call rejected).
3. Phantom Calls
Starting with Release 6, a Third Party Make Call can originate from a station AWOH (Administration Without Hardware), or a hunt group extension administered with members AWOH. This is referred to as a Phantom Call. Event reports for Phantom calls will contain the same information that is included in events provided by other calls placed through Third Party Make Calls. The calling party number (originator) for all the events will always be the station AWOH (Administration Without Hardware), even if the call is originated from a specific hunt group extension, as provided in the Third Party Make Call Request.
a.A Phantom call is similar to a
1.The originator is an extension corresponding to a station AWOH or a hunt group whose members are AWOH.
2.When the DEFINITY ECS detects an incomplete call (busy, intercept), the call is automatically dropped.
3.Phantom Calls cannot be placed on trunks without disconnect supervision.
Phantom calls can be used in conjunction with
Phantom calls can also be placed as Direct Agent calls or priority calls.
Phantom calls are processed normally by call vectoring including Adjunct Routing.
