Example 5 describes calls between a SIP station and a non-IMS SIP element.

Call between a SIP station and a non-IMS SIP element shows the signaling flow associated with a call between a SIP station and a non-IMS SIP element. Communication Manager is administered as either feature server or evolution server.

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

• 2 SIP sessions

  • SIP - Session Manager - Communication Manager

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

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

• Case 1

  Non-IMS SIP Element is a non-SIP endpoint on the same evolution server that’s associated with the SIP station

  • 3 SIP trunk channels

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

• Case 2

  non-IMS SIP Element is a non-SIP endpoint on a different Communication Manager than the one that’s associated with the SIP station or is any other type of non-IMS SIP element as defined at the beginning of the Call Types Encountered in an Session Manager Enterprise section.

  • 2 SIP trunk channels

  • CPU for 2 SIP trunk call legs