No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Voice Feature Guide 01

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Call Service Flows of IP Z Interface Extension

Call Service Flows of IP Z Interface Extension

IP Z interface extension supports many service flows.The following describes the call service flows which include outgoing call service flow for POTS user A, outgoing call service flow for user B with IP Z interface extension, call release flow for POTS user A and call release flow for user B with IP Z interface extension.

Outgoing Call Service Flow for POTS User A

Figure 1-122 shows the outgoing call service flow for POTS user A.

Figure 1-122 Outgoing call service flow for POTS user A

The outgoing call service flow for POTS user A is as follows:
  1. User A picks up the phone, the PBX detects the offhook signal of user A and sends the dial tone to user A, and then user A starts to dial the number. After collecting the number, the PBX plays the ringing tone to the called port, and at the same time plays the ringback tone to user A.
  2. After detecting the ringing tone, MSAN_1 transmits the ringing tone information to the FXS board of MSAN_2 through an RFC2833 packet. After receiving the RFC2833 packet, MSAN_2 restores the analog signals from the ringing tone signals and plays the analog ringing tones to user B.
  3. After hearing the ringing tone, user B picks up the phone. After detecting the offhook signal of user B, the FXS board of MSAN_2 sends the offhook information to MSAN_1 through an RFC2833 packet.
  4. After receiving the offhook information, MSAN_1 sends an offhook acknowledge message to MSAN_2 through RFC2833, and at the same time informs the PBX that user B has picked up the phone.
  5. After receiving the offhook acknowledge message, the entire speech channel is set up, and the call is established between user A and user B.

Outgoing Call Service Flow for User B with IP Z Interface Extension

Figure 1-123 shows the outgoing call service flow for user B with IP Z interface extension.

Figure 1-123 Outgoing call service flow for user B with IP Z interface extension

The outgoing call service flow for user B with IP Z interface extension is as follows:
  1. User B picks up the phone.
  2. MSAN_1 detects the offhook signal of user B and sends the offhook signal through an RFC2833 packet to inform MSAN_2 that user B has picked up the phone.
  3. MSAN_2 sends an offhook acknowledgement message to MSAN_1 through RFC2833, and at the same time sends the offhook signal to the PBX. After receiving the offhook signal, the PBX plays the dial tone to MSAN_1.
  4. MSAN_1 sends the received dial tone to MSAN_2 through RTP streams, and MSAN_2 sends the dial tone to user B.
  5. User B dials the number. The FXS board of MSAN_2 sends the dialed number to MSAN_1 through RTP streams.
  6. The PBX collects the number, plays the ringing tone to user A, and at the same time transparently transmits the ringback tone to user B through RTP streams.
  7. User A hears the ringing tone and picks up the phone. The PBX detects the offhook signal of user A and sends a polarity reversal signal to MSAN_1. MSAN_1 sends the polarity reversal information to MSAN_2 through an RFC2833 packet. MSAN_2 performs polarity reversal billing on user B. By now, the entire speech channel is set up, and the call is established between user A and user B.

Call Release Flow for POTS User A

Figure 1-124 shows the call release flow for POTS user A.

Figure 1-124 Call release flow for POTS user A

The call release flow for POTS user A is as follows:
  1. User A hangs up the phone. The PBX plays the busy tone, and MSAN_1 transparently transmits the busy tone.
  2. After user A hangs up the phone, the PBX restores the normal polarity. MSAN_1 detects the polarity restoration message on the port and sends the information to MSAN_2 through an RFC2833 packet. Then, MSAN_2 restores the polarity of user B.
  3. User B hears the busy tone and hangs up the phone. MSAN_2 sends the onhook event to MSAN_1 through RFC2833 signaling.
  4. When receiving the onhook message, MSAN_1 sends an onhook acknowledgement message to MSAN_2 through RFC2833, and at the same time sends an onhook message to the PBX.
  5. After receiving the onhook message, the PBX releases the call.

Call Release Flow for User B with IP Z Interface Extension

Figure 1-125 shows the call release flow for user B with IP Z interface extension.

Figure 1-125 Call release flow for user B with IP Z interface extension

The call release flow for user B is as follows:
  1. User B connected to the FXS board hangs up the phone. MSAN_2 detects the local onhook event and sends the event to the FXO board of MSAN_1 through RFC2833.
  2. The FXO board sends an onhook acknowledgement to the FXS board through an RFC2833 packet and sends an onhook message to the PBX.
  3. After receiving the onhook message, the PBX plays the busy tone to user A. User A hangs up the phone. The call is released.
Translation
Download
Updated: 2019-02-22

Document ID: EDOC1100067358

Views: 13056

Downloads: 123

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next