Request-Disposition Clause Samples

Request-Disposition. Only the last application in the ‘application chain’ is permitted to perform forking (due to the implications of potentially multiply invoking subsequent applications further down the chain). The SIP INVITE sent towards all Application Servers except the last in the chain (the lowest priority iFC) SHOULD have a Request-Disposition header with a value of ‘no-fork’. In the case of grouped applications (explained in section 2.3) then all of the applications within the group will receive the same value (‘no-fork’) of Request-Disposition. If the last application in the ‘application chain’ requires the ability to fork it cannot be grouped.