Mitel | E1 Trunk noise issues after MiVoice Business Upgrade

Recently we faced an issue with our Mitel IP telephony system after upgrading from version 7 to 8, then to 9.

We’ve Nortel (Currently Avaya) legacy digital telephony system across our businesses and the Mitel IP telephony was implemented with an intention to roll out IP based telephones. Somehow, the solution was partially implemented, forcing us to integrate two different technologies, so that we can make and receive calls from and to both systems.

The digital trunk was created using E1 interface card and everything was working until the software upgrade. We started experiencing a kind of annoying noise, almost impossible to hear the other party & our support partner from Mitel spent 3 weeks trying to figure out what went wrong after the software upgrade.

After 3 weeks of involving different “engineers”, they gave us 3 different possibilities for the noise:

  • Controller’s motherboard have issues
  • Controller’s hard disk is having issues
  • LAN is having bad POE switches

We’ve downgraded from version 9 to 8, “successfully” inheriting the noise issues & and we had a new problem in addition to the noise issues. Handsets started reloading the application once in 2-3 minutes. This is the time we (internal IT team) decided to intervene.

We’ve identified the application reload was happening due to a power failure, which resulted in the IP address used by the Layer 2 (L2) Switch being issued to one of the PCs in the network as it was not excluded with DHCP scope. After spending couple of hours being assigned to address this situation, support partner concluded that “it looks like a hard disk failure”

We took over & started checking for the IPs assigned to the controller and found that it was merely an IP conflict and fixed the reloading issues by releasing the IP (added an exclusion scope with the DHCP server to avoid future conflicts)

However, we had the bigger issue still not resolved, about the noise. As we realized that the support partner is JUST making vague and unrealistic conclusions, requested for the details about codecs and the settings for trunks, which they happily shared with us.

By default, the codec settings for our controller running version 8 has values as seen with the below image.

We toggled all the switches (allowed ones) to No first (Saved), then Yes (Saved) followed by the default settings (refer the image)

Went ahead to “Trunks -> Digital -> Digital Link Descriptors” & re-assigned Voice Encoding to “ADI” (Which the “engineers” set as Nil during their extended support efforts)

Saved the changes and 3 weeks long noise issues were gone in a second.

Although we can’t confirm (technically), it looks like the backup restore after the software upgrade somehow interferes with the codec filtering that needed a manual intervention like the one we did by toggling the switches to NO and Yes & defaults under Codecs section.

If you were frantically searching for solution such a situation like ours, before falling victim to your support partner’s offer to replace the current controller for a discounted price like 4000$, please spend a moment to give what we have tried and succeeded a try.



Oracle Application R12 | Print custom report using CUSTOM.pll

Hello guys,

Happy New Year!

Today we will see how we can use CUSTOM.pll for enabling special menus and printing a custom report by invoking the special menu that we activate using the library.

We are going to use Oracle’s seeded form “POXPOEPO” AKA Purchase Orders.

Please make sure that you make a backup for the CUSTOM.pll prior making below said modifications. CUSTOM.pll is “always” found uner $AU_TOP/resources folder

We’ll enable the SPECIAL15 menu item for the exercise.

Load up CUSTOM.pll using Oracle Forms Designer & make sure you are connected to database before loading the library file.

Attach APPCORE, APPCORE2 libraries with your copy of CUSTOM.pll

Attach FNDCONC.pll library for calling printing related activities

Your CUSTOM.pll should look like the above after attaching said libraries.

Add the block as seen with the image by the bottom of your CUSTOM.pll package body.

     IF (l_form_name = 'POXPOEPO' AND l_block_name = 'PO_HEADERS') THEN	 
    -- 	fnd_message.debug(l_form_name);
     	app_special2.instantiate('SPECIAL15', '&Print', 'prord',TRUE,'LINE');
     END IF;

Now you can proceed with writing code for what happens when “SPECIAL15” event happens

  IF (event_name = 'SPECIAL15') THEN
     IF (l_form_name = 'POXPOEPO' AND l_block_name = 'PO_HEADERS') THEN	 
     	--fnd_message.debug('Will Print This Order');
    --app_special2.instantiate('SPECIAL15', '&Print', 'prord',TRUE,'LINE');
     END IF;

Here, I am calling a procedure that I defined with CUSTOM.pll for handling print requests.

and the package body is as following (not another image, I am going to save some efforts for you)

procedure print_po(p_org_id IN NUMBER, p_order_number IN VARCHAR2) is
		l_ord_num               NUMBER := 0;
		l_ord_type_name         VARCHAR2 (240);
		l_req_id_Rep            NUMBER;
		l_request_completed     BOOLEAN := FALSE;
		l_req_phase             VARCHAR2 (20);
		l_req_status            VARCHAR2 (1000);
		l_req_dev_phase         VARCHAR2 (1000);
		l_req_dev_status        VARCHAR2 (1000);
		l_req_message           VARCHAR2 (1000);
		l_conc_mgr_status       NUMBER;
		p_call_stat             NUMBER;
		p_activep_stat          NUMBER;
		l_order_category_code   NUMBER;
		l_report_name       VARCHAR2 (40);
		l_ret_report_name       VARCHAR2 (40);
		l_req_id 								NUMBER;
		l_order_type_name				VARCHAR2(30);
		l_signing_person VARCHAR2(240);
		l_person_designation VARCHAR2(240);
--fnd_message.debug('Will Print This Order');

/*This is a custom procedure that checks whether the concurrent manager is online or not, you can safely comment this line
   --Check the status of Concurrent Manager
   apps.xx_conc_mgr_status_p (p_call_stat, p_activep_stat);

   IF p_call_stat <> 0
      fnd_message.set_string ('Concurrent Manager Status Unknown');;
      IF p_activep_stat > 0
         NULL;                       --Message('ICM is running' || l_activep);
         fnd_message.set_string (
            'Concurrent Manager is down, Please try printing the invoice later');;
         RAISE form_trigger_failure;
      END IF;
   END IF;

   --Checking concurrent manager status end----
 --  MESSAGE ('Concurrent manager status: up & running');

/* I am picking up the reports names (concurrent_program_name from FND_CONCURRENT_PROGRAMS_VL view as we have different layouts for companies
you can set up a value for l_report_name while variable is defined
   SELECT execution_file_name,STRING1, STRING2
     INTO l_report_name, l_signing_person, l_person_designation
     FROM omspoprintreg
    WHERE 1 = 1 AND organization_id = p_org_id
          AND TRUNC (SYSDATE) BETWEEN start_date_active
                                  AND NVL (end_date_active, SYSDATE);
      fnd_message.set_string (
         'No reports defined for this type of transaction, Please contact OM Super User');;
      RAISE form_trigger_failure;

--   FND_MESSAGE.DEBUG('Printing Order '||p_org_id||' order number '||p_order_number);
   l_req_id :=
      fnd_request.submit_request ('PO',
--You cannot setup :SYSTEM.MESSAGE_LEVEL within CUSTOM.pll, hence use COPY 
--to suppress messages like 'Two records saved'

  -- FND_MESSAGE.DEBUG('Your request id is '||l_req_id);

   l_request_completed :=
      fnd_concurrent.wait_for_request (request_id   => l_req_id,
                                       INTERVAL     => 1,
                                       phase        => l_req_phase,
                                       status       => l_req_status,
                                       dev_phase    => l_req_dev_phase,
                                       dev_status   => l_req_dev_status,
                                       MESSAGE      => l_req_message);
  --:SYSTEM.Message_Level := '25';
  COMMIT; (l_req_id, 'Y');

end print_po;

That’s it!

Now copy the CUSTOM.pll to $AU_TOP/resources & compile it

frmcmp_batch module=CUSTOM.pll userid=apps/apps output_file=CUSTOM.plx module_type=LIBRARY batch=yes compile_all=special

If you don’t have syntax errors or other, you must have the fresh CUSTOM.pll

Please make sure that no users are currently online while you are compiling the CUSTOM.pll (This is only applicable to cases where the CUSTOM.pll is already deployed for different forms)

Log on to the instance, access Purchase Orders form & you should see a new menu item under “Tools” menu enabled

While CUSTOM.pll implements “” by attaching FNDCONC.pll, FORMS personalization will fail to provide the same functionality as most of the seeded forms do not have FNDCONC library attached to them by default. If you don’t want to use to open the completed report, you may create a database level procedure to submit the request(s) and call the same against SPECIAL(n) menu item through FORMS personalization.