Avaya Bell Canada SIP Trunking Service with Business Communication Manager 450 Nota de aplicación descargar pdf (Pagina 5)

TD; Reviewed:

SPOC 3/15/2013

Solution & Interoperability Test Lab Application Notes

5 of 45

BCSIPTrkBCM

behavior of BCM450 with no available resolution at this time. This issue has low user

impact, it is listed here simply as an observation.

3. The BCM450 station which off-net conferences an incoming call from PSTN_1 back

to PSTN_2, displays the improper Calling Party Number. Before the PSTN_2

answered the call, the BCM450 station displayed “Target LineXXX” > “PSTN_2 Calling

Party Number”. After PSTN_2 party answered the call, the display on the BCM450

station changed to “Target LineXXX” - “VoIP Line00X”. It should display the Calling

Party Number of PSTN parties. This is a known behavior of BCM450 with no available

resolution at this time. This issue has low user impact, it is listed here simply as an

observation.

4. The BCM450 station off-net transfers an incoming/ outgoing from/ to PSTN_1 call

back to PSTN_2, the Calling Party Number is not updated. Even the call was

successfully transferred, but BCM450 did not send subsequent INVITE or UPDATE to

Bell Canada on both call legs with the “Contact” or “P-Asserted-Identity” headers

containing the Calling Party Number of the true connected PTSN parties. Both PSTN

parties still displayed the “Pub. OLI” of the BCM450 station. This is a known behavior of

BCM450 with no available resolution at this time. This issue has low user impact, it is

listed here simply as an observation.

5. The 3-way conference call which was initiated by the BCM450 station drops if all

local stations leave the conference. This is a known behavior of BCM450 with no

available resolution at this time. This issue has low user impact, it is listed here simply as

an observation.

6. The Find Me Follow Me (FMFM) users display the “Pub. OLI” of the Virtual

Application DN instead of displaying the original Calling Party Number of PSTN

party. Bell Canada examined the Calling Party Number of outgoing twinned calls so the

“Pub. OLI” of the Virtual Application DN has to be set to one of the subscribed DID

numbers. Otherwise, outgoing calls to FMFM users will be rejected. This workaround

results the original Calling Party Number of PSTN party will not be displayed on the

FMFM users. The FMFM users will display the “Pub. OLI” of the Virtual Application

DN.

7. The off-net call forward unconditional or busy scenarios fail if the forwarded PSTN

party takes longer than 8 seconds to respond. The issue has been seen on the cellular

PSTN phone. BCM450 relies on the respond time of the cellular PSTN phone on the 2

leg to transmit the ringback back to the original calling PSTN party on the 1

leg. If the

respond time is greater than 8 seconds, Bell Canada terminates the call with a CANCEL

request on the 1st call leg. This fails the scenarios. The issue does not happen if the

cellular PSTN phone in good wireless coverage that can significantly reduce the respond

time under 8 seconds limit. The same call scenarios are successful on the regular PSTN

phone (instead of the cellular PSTN party). Bell Canada is recommended to increase the

Session Provisioning Timer to correct the issue. This is acknowledged as a known

1 2 3 4 5 6 7 8 9 10 ... 44 45

Comentarios a estos manuales

Sin comentarios

Avaya Bell Canada SIP Trunking Service with Business Communication Manager 450 Nota de aplicación Pagina 5

Comentarios a estos manuales

Relacionado con productos y manuales para Redes Avaya Bell Canada SIP Trunking Service with Business Communication Manager 450