Designing the VoIP channels

Real time conversion of the call data for transmission in the IP network requires DSP resources at the transitions between IP and non-IP endpoints. They are provided in the form of VoIP channels.

Mitel CPQ (System / AIN view) calculated based on the configured phones, terminals and exchange line circuits, the anticipated traffic load and the VoIP channels required as a result. Both the traffic load within the AIN and the traffic load generated by the exchange transit traffic are taken into account (provided the exchange accesses have been entered). For call connections between two IP endpoints the required VoIP channels for indirect switching are calculated. The result is based on the assumption of an average traffic density. However you have the possibility of manually correcting the calculated value upwards or downwards if required.

Mitel CPQ then assigns the most suitable DSP resources to the calculated VoIP channels and determines the licences required.

Required VoIP channels between two possible end­points

Figure 1.

Non-IP endpoints

IP endpoints
  • Analogue terminal (FXS)
  • Digital system terminal (DSI)
  • DECT cordless phone (DSI)
  • ISDN phone (BRI-S)
  • External via  analogue exchange (FXO)
  • External via ISDN exchange (BRI-T/PRI)
  • Internal voice mail system
  • Auto attendant
  • Internal announcement service
  • Music on hold
  • Conversation recording
  • Announcement with audio file
  • Queue with announcement
  • Conference bridge
  • IP system phone
  • Mitel SIP terminal
  • Standard SIP terminal
  • DECT cordless phone via SIP-DECT
  • WiFi cordless phone via SIP-DECT
  • WiFi cordless phone via SIP access point
  • WiFi mobile phone via AMC controller
  • External via SIP provider
Note:

In normal operation all IP endpoints are logged on to the Master, even if locally they are situated near a satellite.

Parent topic: TDM-DECT
↑