Messages

1

Mitel MiVoice Business/MCD/3300 / EDT TRACE TSP L2L3 Link #

« on: November 19, 2020, 02:36:28 PM »

Good afternoon,

I have an issue in one of our site in Jakarta where the user is trying to call forward his phone to an a cell phone as Call forward always.  All COR and COS allows the call to go out but it seems we are blocked from the provider. When we call, we get a message that the call can not complete as number is incomplete. So I assumed that the on the EURO ISDN protocol, I could use the ENBLOC to send as a full number but it is always the same message. Our CPN substitution is configured as 2550XXXX (I block the number ) which is the main number. The Public Trunk to Public trunk is enabled the COS we need to have it on.  Below is a copy/paste of the EDT TRACE TSP L2L3 5 1 2 1.

It seems that the call is bouncing back in to the MCD from the provider and at one point the cal is rejected.  Can someone explain to me if I am wrong.

Is there also some kind of document on this EDT TRACE Command that explain the log file?

2020-11-19  03:07:57  Link 3  - To Mitel   - HLen 4, ILen 44, IType 6  this is from the PROVIDER
SAPI 0 TEI 0 C/R 1 P/F 0 NR 100 NS 73 INFO Orig PD=0x8 CR=0x1f52  SETUP(0x5)
1   10100001 Information Element: Sending Complete:
1   00000100 Information Element: Bearer Capability:
2   IE Length                   : 3  octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---00000 Info. trans. cap.  : Speech
4   1------- Extension bit      : Not Continued
    -00----- Transfer Mode      : Circuit Mode
    ---10000 Info. trans. rate  : 64 kbits/s
5   1------- Extension bit      : Not Continued
    -01----- Layer identifier   : 1
    ---00011 Layer 1 protocol   : Rec. G.711 A-law
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----0--- Indicated channel  : preferred
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0011111 Channel Number     : 31
1   00011110 Information Element: Progress Indicator:
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- Spare              : Spare
    ----0010 Location           : Public network serving the local user
4   1------- Extension bit      : Not Continued
    -0000001 Description        : Call is not end-to-end ISDN
1   01101100 Information Element: Calling Party Number:
2   IE Length                   : 15 octets
3   0------- Extension bit      : Continued
    -001---- Type of number     : International
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
3a  1------- Extension bit      : Not Continued
    -00----- Presentation       : Allowed
    ---000-- Spare
    ------11 Screening          : Network provided
4   ******** Phone number       : [0062210000007] This is the provider number somehow
1   01110000 Information Element: Called Party Number:
2   IE Length                   : 5 octets
3   1------- Extension bit      : Not Continued
    -100---- Type of number     : Subscriber number
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
4   ******** Phone number       : [7890]                 DID NUMBER

2020-11-19  03:07:57  Link 3  - From Mitel - HLen 4, ILen 10, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 74 NS 100 INFO Dest PD=0x8 CR=0x1f52  CALL PROCEEDING(0x2)
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0011111 Channel Number     : 31

2020-11-19  03:07:57  Link 3  - From Mitel - HLen 4, ILen 9, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 74 NS 101 INFO Dest PD=0x8 CR=0x1f52  DISCONNECT(0x45)
1   00001000 Information Element: Cause: 
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- spare 
    ----0000 Location           : User
4   1------- Extension bit      : Not Continued
    -0010101 Cause code         : call rejected                                

2020-11-19  03:07:57  Link 3  - To Mitel   - HLen 4, ILen 5, IType 5                                                                From the provider back to the client
SAPI 0 TEI 0 C/R 1 P/F 0 NR 102 NS 74 INFO Orig PD=0x8 CR=0x1f52  RELEASE(0x4d)

2020-11-19  03:07:57  Link 3  - From Mitel - HLen 4, ILen 5, IType 5                                      From the Mitel System back to the Provider
SAPI 0 TEI 0 C/R 0 P/F 0 NR 75 NS 102 INFO Dest PD=0x8 CR=0x1f52  RELEASE COM(0x5a)

2020-11-19  03:07:59  Link 3  - To Mitel   - HLen 4, ILen 44, IType 6                                      From the provider back to our client
SAPI 0 TEI 0 C/R 1 P/F 0 NR 103 NS 75 INFO Orig PD=0x8 CR=0x1f53  SETUP(0x5)
1   10100001 Information Element: Sending Complete:
1   00000100 Information Element: Bearer Capability:
2   IE Length                   : 3  octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---00000 Info. trans. cap.  : Speech
4   1------- Extension bit      : Not Continued
    -00----- Transfer Mode      : Circuit Mode
   ---10000 Info. trans. rate  : 64 kbits/s
5   1------- Extension bit      : Not Continued
    -01----- Layer identifier   : 1
    ---00011 Layer 1 protocol   : Rec. G.711 A-law
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----0--- Indicated channel  : preferred
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0000001 Channel Number     : 1
1   00011110 Information Element: Progress Indicator:
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- Spare              : Spare
    ----0010 Location           : Public network serving the local user
4   1------- Extension bit      : Not Continued
    -0000001 Description        : Call is not end-to-end ISDN
1   01101100 Information Element: Calling Party Number:
2   IE Length                   : 15 octets
3   0------- Extension bit      : Continued
    -001---- Type of number     : International
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
3a  1------- Extension bit      : Not Continued
    -00----- Presentation       : Allowed
    ---000-- Spare
    ------11 Screening          : Network provided
4   ******** Phone number       : [0062210000007]
1   01110000 Information Element: Called Party Number:
2   IE Length                   : 5 octets
3   1------- Extension bit      : Not Continued
    -100---- Type of number     : Subscriber number
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
4   ******** Phone number       : [7890]

2020-11-19  03:07:59  Link 3  - From Mitel - HLen 4, ILen 10, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 76 NS 103 INFO Dest PD=0x8 CR=0x1f53  CALL PROCEEDING(0x2)
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0000001 Channel Number     : 1

2020-11-19  03:07:59  Link 3  - From Mitel - HLen 4, ILen 9, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 76 NS 104 INFO Dest PD=0x8 CR=0x1f53  DISCONNECT(0x45)
1   00001000 Information Element: Cause: 
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- spare 
    ----0000 Location           : User
4   1------- Extension bit      : Not Continued
    -0010101 Cause code         : call rejected                               

03:07:57 RI230 DPN 2B ISRM_I  ;10;*3#*19*Z#*58*Ca*1*Z#*233*`IBc#*58*CI*W6a#     
03:07:57 RI230 DPN 17 SSRM_C  *50*0062210000007#7890                           
03:07:57 RO230 DPN 2  CRM/CIM ;29;                                             
03:07:57 RI230 DPN 2  CRM/CIM ;29;                                             
03:07:59 RI201 DPN 2B ISRM_I  ;10;*3#*19*Z#*58*Ca*1*Z#*233*`IBc#*58*CI*W6a#     
03:07:59 RI201 DPN 17 SSRM_C  *50*0062210000007#7890                           
03:07:59 RO201 DPN 2  CRM/CIM ;29;                                             

2

Mitel Software Applications / Re: MiCollab rel 9.1

« on: July 15, 2020, 08:56:10 AM »

No, we have the Virtual Machine and it is release MiCollab 9.1.0.15-01

I have disabled the MBG because we are not using it at this time thinking that might solve the issue. I also turned of RC4 in the Client Service but same result, those warning come within seconds and within 2 minutes, I have about 60 of thoses

thanks

3

Mitel Software Applications / MiCollab rel 9.1

« on: July 15, 2020, 07:42:12 AM »

Good day to you,

We recently upgraded our VMAS from release 6 to 7.3 then to 9.1.  Since then we are getting numerous warning alarms such as this one:  MiCollab Alarm- INM_wd Shutdown, Module WSP pid 1430 is shutting down. 

We are not using MBG and I checked the MiCollab Client Service, everthing is fine. I have the RC4 enable but we do not use MBG, as per the description, it would seem that if we use MBG we need to have this option enabled.

Not sure what this warning message is, it is piling up during day time, I have numerous warning with different PID number.

Input please.

4

Mitel MiVoice Business/MCD/3300 / Re: Nupoint Transfer to speed dial not working

« on: April 08, 2020, 03:04:57 PM »

NEPphoneguy,

Yes within the MCD it does work that is why I am surprised. Public to Public is configured, COR matches for NUPOINT for making an outside call. Speed Dial has the Override selected.

5

Mitel MiVoice Business/MCD/3300 / Re: Nupoint Transfer to speed dial not working

« on: April 08, 2020, 03:01:34 PM »

that is what the original script was. I am trying to understand why it is working with the work around i created vs having a blind transfer to an external number via a speed dial. That speed dial is 2 level down in the original call flow: main call flow and then language selection, then the transfer.

6

Mitel MiVoice Business/MCD/3300 / Nupoint Transfer to speed dial not working

« on: April 08, 2020, 01:03:01 PM »

Good afternoon,

I am trying to understand the logic behind Nupoint as to why it is not working when selecting an option in a call script pointing to a speed dial -> outside number but, if i changed my selection in my script to an existing number in the MCD, this extension in turn is rerouted to the same speed call, the call transfer works.

Here is my set up:

Main number for the company is a DID pointing to LOCXXXX, this is day day script with language selections. The caller will select language selection to be English for example then get to the company script using a MENU with option 1, 2, 3, 4 for instance and to reach sales they can then select 5. If i point this selection directly to a speed dials which in turn dials 9+XXXXXXXXXX, I get `extension XXXXXXX ( speed call number ) is unavailable.

So, i found 2 x ways to do it: doing the same kind of set up, instead of pointing the selection to a speed-dial, i am using a real extension number within the MCD, this extension number is rerouted always to my speed dials and the call goes out no issue.   The second way, is to point my selection from my script to Voicemail making it a Call flow then i can used a selection or a blind transfer to that external number and it works.

My question: is it possible that for some unknown reason, if you enter a call flow and make a selection within that call flow to go to another call flow, Nupoint just does not allow a call to go externa via a speed diall?  that is the only explanation i find.

Again, the 2 solutions i created works fine.

Thanks

YB

7

Mitel MiVoice Business/MCD/3300 / Re: block all incoming calls on a single extension

« on: May 29, 2019, 05:27:47 PM »

you may want to use the interconnect table, that could be a way to do it

8

Mitel MiVoice Business/MCD/3300 / Re: Call drops after 3.5 rings on a blind transfer to cell phone

« on: May 20, 2019, 05:33:18 PM »

Hello,

unsure but i will check as i am returning back to work tomorrow. I was not sure about this option. Thanks, first thing to do tomorrow morning

9

Mitel MiVoice Business/MCD/3300 / Call drops after 3.5 rings on a blind transfer to cell phone

« on: May 17, 2019, 12:59:51 PM »

Hello everyone,

I have a funny condition that started not long ago where for some unknown reasons, the Nupoint ports after transferring call to a cell phone, the call drops after 3.5 rings.

Here is the set-up. We have a huge network ( international and local )and is configured with Mitel Gateways, VM MCD's and stand-alone VMAS. We have 1 Gateway for incoming calls, 1 x gateway for outgoing calls. Calls are coming in via MCD Gateway on a T1 (PRI), the DID number is configured to call reroute to Voicemail, Voicemail ports are located to another gateway. Our network is set with Voicemail Release 6 and MCD 7.2 SP1 PR1. We are in the process of upgrading to Release 8 on the Voicemail and release 8 to our MCDs. We will proceed to release 9 on MCD after.

This portion of incoming call to voicemail works fine. That number is configured to a Call flow for On call technician, during day time it rings to a specific key on 5 phones to be picked up, after hours, there is a blind transfer to an external cell phone, call goes out to cell phone to a different MCD gateway but after 3.5 rings, the call drops.

We monitor the call going to voice mail, we can stat the port going busy, once the blind transfer is made, the port goes idle but on the IP Phone display it shows: Call Held by " port number ", then it drops.

We monitored what happens if we changed the blind transfer from cell phone to an internal number if we had the same condition. Nope, the internal phone rings and does not drop.

We check all timers, COS for Nupoint ports ( they are making the blind transfer ), we think there is a recall somewhere but we can not figure out why.

Any of you guys ever experienced this???

Thanks for any help.

10

Mitel MiVoice Business/MCD/3300 / Re: Call rerouting night 1 - night 2 for the console

« on: January 29, 2019, 12:12:28 PM »

Yes I know that MCD has no interaction with NUPOINT, thus my point about Night2.

Understand that our client main number is directly going to Nupoint with a day script ( including the Holidays and working hours schedule ). Again, anytime in our scripts someone dials 0 when the option is available, the calls are routed to the main attendant console at extension XXX-3001.

Call rerouting for XXX-3001 is scheduled to CCR always: Day 1 being no rerouting. Night 1, is rerouted always to Nupoint. This rerouting allows the console to have a script and mailbox providing callers to either leave a message to be retrieve later or dial another number for immediate assistance.

Call rerouting Night 2, is my concern. Again, I am trying to be clear, as the number being dialed from the day script is XXX-3001, this number will always follow even in Night 2 mode. I created XXX-5000 as a phantom DN on one NUPOINT port, created the call rerouting always to Nupoint for XXX-5000 and pointed the Night 2 for XXX-3001 to this new number but it just does not follow or go.

The clients are asking to bypass the Nupoint Schedule during working hours to go to Night Service if they have to close their business early for whatever reason. I know that NIGHT 2 mode does not interact with Nupoint, that is why I am trying to figure out a way for that Night 2 to point to my Night Script number being XXX-2001. I tried to reroute to XXX-2001 but it just does not work.

Our clients do not have ACD because they do not have call center. I know that I could get by somehow but they do not want to pay for a package that will not be used.

Again, thanks for your time and help

11

Mitel MiVoice Business/MCD/3300 / Call rerouting night 1 - night 2 for the console

« on: January 24, 2019, 06:56:29 PM »

Hello everyone,

I have been working on the Mitel 3300 for 3 years now as installers and now as Voice Support. We have more and more request nowadays by our clients asking that the main console be put in Night mode 1 during day time enabling the receptionist to be able to just walk away in case she needs to deliver something to a colleague, but also the clients want the console to be put in night 2 mode to enable the night treatment.  Our set-up is quite simple and standardized across our network.

1. Main number being a DID is converted as actual number to number XXX-YYYY. That is rerouted to Nupoint which in turns offers a script including Holiday schedule and Weekly Schedule.
2. at any instance, a caller can dial 0 to be transferred to the reception for help.
3. our reception is XXX-3000 but Ext XXX-3001 is the number dialled when pressing 0 in the script, call rerouting DAY is set to 1, so she can answer the calls, Call rerouting Night 1, is rerouted always to Voicemail. This option is for the reception to go to Voicemail, created a mailbox XXX-3001 as TREE, In Nupoint, i created Call Flow XXX-3001, so we offer the caller with a message stating that receptionist is unavailable for short time, if the call is urgent the can press 1, blind transfer to another extension to be answered for this emergency or press 2 to leave a message. That Voicemail has a Message Waiting Indicator on an IP set at reception. So reception knows that there is a message to be retrieved. This works fine.  My problem that i can not figure out is how do i configure the NIGHT 2 to get the night script and bypass the working scheduled configured in Nupoint.  As XXX-3001 is the root of the call once transferred from Nupoint, this is the number that will always be recognized but I just can not figure out how i can trigger that night script from the NIGHT 2 option on the console.

I am originally a Nortel Products technician and was very easy with the IDC table to change DAY/NIGHT option from the console, there was a direct relation to the Incoming Digits Conversion table. Mitel does not really offer the same option. Mitel is completely a different thinking and logic

I have been reading and trying to figure out how to use NAMETAG HUNT Group, but i am not really sure how to do it. I tried the call rerouting, no more success. Any ideas?

Thanks for any help

12

Mitel MiVoice Business/MCD/3300 / Re: ICP Comms Card

« on: February 04, 2018, 12:04:34 PM »

we had the same issue not long ago and it was discovered by one of my colleague that it relates to the inactivity timer on the IPX trunk. If the timer is not configured, the ICP COM Card will trigger an alarm. We could not figure it out until she took some notes. Our network has more than 300 elements but we would get those alarms randomly not knowing why.

Configure the inactivity timer to 1 hr or 30 min, it has to match at both ends ( meaning that if one of you MCD is for a satellite office, your main PBX at the main office must match the same inactivity timer as your satellite ). If that inactivity timer is not configure and no calls are made, the link will remain up indefinitely preventing calls to be made.

Just try it, it may solve your issue

13

Mitel MiVoice Business/MCD/3300 / Re: What Class of Service applies to a non-prime line?

« on: December 14, 2017, 07:14:44 PM »

Multicall non-prime line does not use COS, if you want to make a forward on this multi call extension, unsure if you can use call rerouting as this is not a single line but multi call.... needs to try

14

Mitel MiVoice Business/MCD/3300 / Re: Message wait key calls HCI reroute group

« on: September 29, 2017, 08:06:54 PM »

is your HCI reroute MWI in Nupoints configured properly? we use the loc code + 40... there is not too many thing to be configured.
but there is also another thing that you may look at that is not mentioned, check the features for that extension. That message waiting light may also be a Call back message light. Perhaps that feature is active and not being looked at

15

Mitel MiVoice Business/MCD/3300 / Re: User Unable To Transfer External Calls Internally.

« on: September 28, 2017, 06:43:44 PM »

how does he /she perform the transfer? might be stupid but the transfer must be configure in the COS and also the way of doing transfer might be just wrong. Must press the transfer button ( arrow / with faces ) next to hold button and dial the extension and hang up if the transfer is unannounced transfer