When this attribute is set to 1 the retry after support is enabled for the following scenario. When MTAS receives a re-INVITE request, whilst still waiting for the ACK (200 OK) for the pending (re)INVITE transaction, it will send a 500 final response including a Retry-After header. The MTAS node is acting as UAS in this case.