Succession 3.0 upgrade issue

[dixiedogger]

Has anyone had any issues with external calles forwarding to menus? After upgrading to 3.0 any external calls that were forwarding to MM menus now say "the subscriber "forwarding number" does not subscribe to this service". Like it was an internally forwarded call. I have found a work around by placing the forwarding number in the vsdn table but INMHO you should not have to do this. External calls have always followed the called number not the forwarding number.

 

[dummyspy]

did anyone have solution to this issues.

 

[tellyteck1]

here is the information from Nortel. AJK

Title
BURST'S OF WHITE NOISE HEARD BY ORIG AND TER PARTYS DURING ESTABLISHED CALL.



Problem Description
Problem Text:
When on call the caller and the destination both hear burst of white
noise.

Setup and actions performed to cause the problem:
Option 11C using SIPE. When the agent gets a call or makes a call outside
there is a burst of white noise that could disapear after a few seconds or
continue for as long as the call is active.

Expected Results:
Call should be normal without any burst of white noise

Actual Results:
Calls should be clear with no white noise.

Impact of problem
Very annoying to the customer since both the caller and destination can
hardly converse with this burst of white noise which sometimes can extend
as long as the call is active.



Notes
NOTE: These patches needs to be installed in both MAIN and EXPANSION cabinets. Or in CSE terminology call server and Media Gateway. AN INI (Initialization) is REQUIRED on MAIN/CS and EXPANSION/MG. Here is the procedures to install or replace the patch mplr15960: If you replace the old patch mplr15960 with the new patch mplr15960 issue #2: 1) take the old patches out of service (poos) and remove the patches from memory (pout) 2) reboot the system ( if you don't reboot, the system may warmstart by itself with BERR705) 2) load and activate the new patches on all cabs 3) reboot the system again. If you only install the new patch mplr15960 issue #2: 1) load and activate the new patches on all cabs 2) reboot the system

 

[0ut3rbank5]

Hey, All. Coming back with a fix since my problem in Nov. after Succession 3.0 upgrade from Rls. 25.40. My problem was fixed with this patch:
PRS/CR: Q00520526 under the name p16732_1 (filename: p16732_1.cpt). Ask your vendor.