Call Diversion is the change of the destination of a call.
There is a wide range of call diversion types available. Examples are Call Diversion Unconditional, Call Diversion on No Reply, Call Diversion on Busy, Call Diversion on Not Logged-In.
Enterprise diverts call to Service Provider:
The Enterprise system MUST be able to divert a call to a Service Provider.
Enterprise sends requests and responses to Service Provider:Service Provider diverts call to Enterprise:
The Enterprise system MUST be able to send an INVITE request which contains a Diversion header field with the URI of the diverting party as well as the diversion reason. Furthermore, sending a P-Asserted-Identity header field with the identity of the calling party SHOULD be supported in order to allow updating the client display.
Enterprise receives requests and responses from Service Provider:
Service Provider sends requests and responses to Enterprise:
Service Provider receives requests and responses from Enterprise:
The Service provider SHOULD be able to process a received INVITE request containing a Diversion header field.
The Service Provider MAY support diverting calls to the Enterprise system or MAY pass diverted calls to the Enterprise system.
Currently no support for actively diverting calls to the Enterprise system using the Diversion header field is available from any Service Provider. Therefore, for the Enterprise system this diverted call is just like a new incoming call.
The following image depicts a call diversion scenario where the Diversion destination is at the Service Provider side:
The calling party A@N1 calls the diverting party B@N2. This call gets diverted to C@N3, for example, due to a received indication from the client or due to a configured call diversion within the Enterprise system, by sending a new INVITE request to the diverted-to destination at the Service Provider side. This new INVITE request may contain a Diversion header field which indicates that this call is a diverted call.
Parent topic: SIP Trunking overview