Example 10 describes calls between Communication Manager administered as an evolution server or a non-SIP Communication Manager and the PSTN.
We assume that the Communication Managers and non-SIP Communication Managers in a Session Manager enterprise supports their own non-SIP trunks directly to the PSTN.
Session Manager SIP sessions required per call for various call types summarizes the number of SIP sessions involved per Session Manager instance for each of the calls described in the Call Types Encountered in an Session Manager Enterprise section.
Table 1: Session Manager SIP sessions required per call for various call types
Endpoints involved in the call |
SIP sessions per SM |
Two Avaya SIP stations registered to the same Session Manager instance, using the same Communication Manager administered as either a feature server or evolution server. |
3 |
Two Avaya SIP stations registered to the same Session Manager instance, using different Communication Managers administered as either feature servers or evolution servers |
3 |
Two Avaya SIP stations registered to different Session Manager instances, using the same Communication Manager administered as either a feature server or evolution server. |
2 |
Two Avaya SIP stations registered to different Session Manager instances, using different Communication Managers administered as either feature servers or evolution servers |
2 |
An Avaya SIP station and a non-IMS SIP element |
2 |
An Avaya SIP station and a non-SIP Communication Manager or the PSTN |
2 |
Two non-IMS SIP elements |
1 |
A non-IMS SIP element and a non-SIP Communication Manager |
2 |
Two non-SIP Communication Managers |
1 |
A Communication Manager as an access element or non-SIP Communication Managerand the PSTN via non-SIP trunks |
— |
Communication Manager core resources required per call for various call types summarizes the number of SIP trunk channels per Communication Manager administered as either a feature server or evolution server, the number of SIP trunk call legs per Communication Manager administered as either a feature server or evolution server, and the number of non-SIP trunk call legs per Communication Manager administered as either a feature server or evolution server for each of the calls described in the Call Types Encountered in an Session Manager Enterprise section.
Table 2: Communication Manager core resources required per call for various call types
Endpoints involved in the call |
SIP trunk call legs per FS or ES |
Non-SIP trunk call legs per FS or ES |
Two Avaya SIP stations registered to the same Session Manager instance, using the same core Communication Manager as a feature server |
2 or 41 |
NA |
Two Avaya SIP stations registered to the same Session Manager instance, using different core Communication Managers as feature servers |
2 |
NA |
Two Avaya SIP stations registered to different Session Manager instances, using the same core Communication Manager as a feature server |
2 or 4 1 |
NA |
Two Avaya SIP stations registered to different Session Manager instances, using different core Communication Managers as feature servers |
2 |
NA |
An Avaya SIP station and a non-IMS SIP element |
2 or 32 |
0 or 1 2 |
An Avaya SIP station and a non-SIP Communication Manager or the PSTN |
3 |
1 |
Two non-IMS SIP elements |
NA |
NA |
A non-IMS SIP element and a non-SIP Communication Manager |
3 |
1 |
Two non-SIP Communication Managers |
2 |
2 |
A Communication Manager as access element or non-SIP Communication Manager and the PSTN via non-SIP trunks |
NA |
1 |
1SIP trunk channels per call if evolution server; 4 SIP trunk channels per call if feature server
2For a call between an Avaya SIP station and a non-IMS SIP element, the only time the larger numbers apply are when the non-IMS SIP element is a non-SIP endpoint on the same evolution server that is associated with the SIP station.
|
Each non-SIP Communication Manager involved in a call with another element in the Session Manager enterprise requires one non-SIP trunk channel for that call.
