Example 8 describes calls between a non-IMS SIP element and a non-SIP Communication Manager administered as either a feature server or evolution server.

Call between a non-IMS SIP element and a non-SIP Communication Manager shows the signaling flow associated with a call between a non-IMS SIP Element and a non-SIP Communication Manager.

Session Manager resources associated with the call depicted in Figure : 1 include:

• 2 SIP sessions

  • non-IMS SIP Element - Session Manager - Communication Manager

  • Communication Manager - Session Manager - Communication Manager

  Note:

  The signaling path from Session Manager to Communication Manager to Session Manager consists of two IMS SIP legs if Communication Manager is a feature server or two non-IMS legs if Communication Manager is an evolution server.

Communication Manager resources associated with the call depicted in Figure : 1 include:

• 3 SIP trunk channels

• 1 non-SIP trunk channel

• CPU for 3 SIP trunk call legs and for 1 SIP non-SIP trunk call leg