Release codes

When the call ends, all its legs are stored in database. But in the most common case, when the hunting takes place, they are stored with different release codes.

If the call incomes into the Softswitch and it has no routes in hunting, its inbound call leg is stored with disposition “NO ROUTE”.

If the call incomes into the Softswitch and it fails balance authorization, its inbound call leg is stored with disposition “NO BALANCE”.

If the call incomes into the Softswitch and it fails to be billed (for example if there is no price for this code), its inbound call leg is stored with disposition “FAILED”.

If the call incomes into the Softswitch and it has some routes and the router hunts on them, the inbound leg's disposition will be the same as the last call leg's in hunting. The outbound call legs will be stored with dispositions, that we returned by Asterisk Dial() application.

Hunting proceeds to the next route in case if Asterisk's Dial() return code differs from “CANCEL”,”ANSWER”,”NOANSWER”,”BUSY”.