Messages

1

Mitel MiVoice Business/MCD/3300 / How to stop a user dialling full ddi number for internal extension?

« on: July 25, 2012, 11:22:00 PM »

Guys,
we have a range of customers all using the PABX each with a 4 digit extension number that matches the last four digits of the respective ddi range. However many users still dial the full ddi instead of the extension number. What i want to do is avoid paying toll charges for any calls between extensions when the full ddi number is dialled. i assume it is somewhere within the ARS tables but cant see how terminate the route selection where the ddi prefix has been dialled.
Because we have a 4 x 100 number ranges and 2 x E1 links this is starting to get a bit costly.
A few pointers in the general direction would be great.
Thanks

2

Mitel MiVoice Business/MCD/3300 / Re: 5312 Keys template

« on: July 01, 2012, 08:37:38 PM »

All,
i had another request for mine too, so here it is.
5312, 5224 & PKM.
Cheers

3

Mitel MiVoice Business/MCD/3300 / Call forwarding - Something simple?

« on: May 25, 2012, 01:27:44 AM »

Guys,
sure I am missing something here but cant get call forwarding to work as the customer wants.
Running MCD5.0
I have configured 1st alternate as the voicemail Pilot number and then put a handset call forward no ans to 7263 on 7262.
1. call to 7262, if not answered then forward to 7263, if not answered here, then drop to voicemail mbx 7262. This works fine.

However the customer also wants this to happen if he is on the phone so.....
2. call to 7262, if busy, requires call waiting, then if not answered forward to extn 7263, if not answered here, then drop to voicemail into mbx 7262.
the first part works fine and I get the 'call waiting' in the display and the call goes off to 7263 as required, however it just wont then go to the voicemail.

I will need this to happen for both internal and external incoming calls. At the moment have only tried it for internal calls, but will keep experimenting anyway.

I am sure it is something simple maybe a timer or COS flag but starting to pull my hair a little.

Any help would be greatly appreciated

Cheers
Chris

4

Mitel MiVoice Business/MCD/3300 / Re: MCD 5.0 SP1 & 5320 DHCP

« on: April 26, 2012, 09:19:18 PM »

Ralph, not far off actually.
what we have found is that the switch is by default using CDP, and the vlan associated with the CDP is VLAN100 (default Cisco). even though we deleted VLAN100 from the switch the CDP Field still showed it. The phone was booting and must have been getting the CDP because as it was going through the boot process we could see the vlan was going to VLAN 0? anyway when we turned CDP off on the switch all was ok. We also left CDP on but deleted the VLAN number which had the effect of putting a 0 in the VLAN field on the switch, which we couldn't do manually as VLAN 0 is not a valid VLAN?? Anyway, with CDP on and VLAN field set to 0 the phone then booted with VLAN NONE, and away to go.
Interestingly enough none of this affected the 5312 handset that we had connected too.
Thanks for the help all.

5

Mitel MiVoice Business/MCD/3300 / Re: MCD 5.0 SP1 & 5320 DHCP

« on: April 26, 2012, 01:42:17 AM »

The statically assigned phone IP disappears when it reboots after saving the config.
However, it kind of looks like a problem between our switch (cisco esw520) and our WAN router. When we plug the phone direct into the router, it worked without any static info. Put back to the switch didn't work.
Did a bit more testing and then all of a sudden it works with DHCP plugged into the switch.
we think it may have something to do with the VLAN tagging but still trying to figure it out. done a few woreshark traces but nothing looks out of the ordinary.

6

Mitel MiVoice Business/MCD/3300 / Re: MCD 5.0 SP1 & 5320 DHCP

« on: April 25, 2012, 10:05:14 PM »

Thanks BlueWhite4 I'll get one raised, although here in OZ we go through a distributor not straight to MITEL and its much harder to get things resolved. 
We tried putting a static on the phone but when it goes through it's boot up it says CONTACING ICP and still cant communicate. When we then check the Static IP settings the IP address is not in the IP V4 Settings
Cheers

7

Mitel MiVoice Business/MCD/3300 / MCD 5.0 SP1 & 5320 DHCP

« on: April 25, 2012, 09:02:30 PM »

Guys having real issues with 5320's working at remote sites now that we have gone to MCD5.0.
Our sites are all within our private network and they use the Teleworker option with the private IP of the controller to communicate and get their upload.
However on going to MCD5.0 the 5320 handsets just sit there at DHCP Discovery, but only when on a managed switch that has VLAN's enabled. The phones are always in the default VLAN and we just cannot get them to work.
I know there is a MITEL article on this but it does not help.
Has any one got any ideas on how i can configure the phone or the switch to get around the DHCP Discovery.
By the way the DHCP server is a WAN device and does not have the option to add DHCP Options. the ARP table shows that it has alloctaed the IP to the phone but the phone doesn't seem to acknowledge this. 

8

Mitel MiVoice Business/MCD/3300 / Outgoing CLI from incoming Sip trunks

« on: November 28, 2011, 10:46:12 PM »

Guys,
having issues trying to get outgoing CLi correct when calls are coming in from our SIP server. I have added a correct CPN number into the SIP peer profile but still doesn't display. My main CPN substitution form is correct as other numbers work fine. When i look at my SMDR the call is coming in from X999. i have used a tag for smdr and this shows in the SMDR for the outgoing call. Any pointers? see SIP profile and SMDR trace below.

 11/29 02:14P 00:00:04 T940  006 00870029919                 T100               
     1                                                                         
 11/29 02:14P 00:00:04 X999      0870029919                A T100


Call Routing and Administration Options
  Interconnect Restriction   1   
  Maximum Simultaneous Calls   5   
  Outbound Proxy Server   SLIPPERPy   
  SMDR Tag   940   
  Trunk Service   5   
  Zone   1   
  Alternate Destination Domain Enabled   No   
  Alternate Destination Domain FQDN or IP Address       
  Enable Special Re-invite Collision Handling   No   
  Private SIP Trunk   No   
  Route Call Using To Header   No   
 
 
Calling Line ID Options
  Default CPN   0870718940   
  CPN Restriction   No   
  Public Calling Party Number Passthrough   No   
  Use Diverting Party Number as Calling Party Number   No   
 
 
Authentication Options
  User Name       
  Password   *******     
  Confirm Password   *******     
  Authentication Option for Incoming Calls   No Authentication   
  Subscription User Name       
  Subscription Password   *******     
  Subscription Confirm Password   *******     
 
 
SDP Options
  Allow Peer To Use Multiple Active M-Lines   No   
  Allow Using UPDATE For Early Media Renegotiation   No   
  Avoid Signaling Hold to the Peer   No   
  Enable Mitel Proprietary SDP   No   
  Force sending SDP in initial Invite message   No   
  Force sending SDP in initial Invite - Early Answer   No   
  Limit to one Offer/Answer per INVITE   No   
  NAT Keepalive   No   
  Prevent the Use of IP Address 0.0.0.0 in SDP Messages   No   
  Renegotiate SDP To Enforce Symmetric Codec   No   
  Repeat SDP Answer If Duplicate Offer Is Received   No   
  RTP Packetization Rate Override   No   
  RTP Packetization Rate   20ms   
  Special handling of Offers in 2XX responses (INVITE)   No   
  Suppress Use of SDP Inactive Media Streams   No   
 
 
Signaling and Header Manipulation Options
  Allow Display Update   No   
  Build Contact Using Request URI Address   No   
  De-register Using Contact Address not *   No   
  Disable Reliable Provisional Responses   Yes   
  Disable Use of User-Agent and Server Headers   No   
  Enable sending '+' for E.164 numbers   No   
  Force Max-Forward: 70 on Outgoing Calls   No   
  Ignore Incoming Loose Routing Indication   No   
  Only use SDP to decide 180 or 183   No   
  Require Reliable Provisional Responses on Outgoing Calls   No   
  Use P-Asserted Identity Header   Yes   
  Use P-Preferred Identity Header   Yes   
  Use Restricted Character Set For Authentication   No   
  Use To Address in From Header on Outgoing Calls   No   
  Use user=phone   No   
 
 
Timers
  Registration Period   3600   
  Registration Period Refresh (%)   50   
  Session Timer   90   
  Subscription Period   3600   
  Subscription Period Minimum   300   
  Subscription Period Refresh (%)   80   
 
 
Key Press Event Options
  Allow Inc Subscriptions for Local Digit Monitoring   No   
  Allow Out Subscriptions for Remote Digit Monitoring   No   
  Force Out Subscriptions for Remote Digit Monitoring   No   
  Request Outbound Proxy to Handle Out Subscriptions   No   
  KPML Transport   default   
  KPML Port   0   
   

9

Mitel MiVoice Business/MCD/3300 / Re: Outgoing CLI

« on: November 14, 2011, 11:48:28 PM »

Thanks MitelUK2010, associated directory number worked a treat.
Didn't really know that form existed or what it did.
Cheers
Chris

10

Mitel MiVoice Business/MCD/3300 / Outgoing CLI

« on: November 13, 2011, 06:30:20 PM »

We have a customer CXIIi connected by IP trunks to our 3300 MXE. Both are running MCD 4.2. The customer site only has access to the PSTN via a PRI link on our MXE. The PRI link is dedicated for their use only. Problem is that their site is 3 digit numbering and our's is 4 digits and when it comes to outgoing CLI on their link only the main number is being presented. I have gone to add the 4xx to the CPN substitution form but as the current entries are 4 digit i cant add the 3 digit.
Is there any way to change the presentation of the outgoing CLI from the customer PABX over the IP trunks so that it presents 4 digits (94xx) instead.
The customer does not want 4 digit dialling on site.
Hopefully this makes sense.
Cheers
Chris

11

Mitel MiVoice Business/MCD/3300 / Re: Clusters - Do I need them

« on: October 14, 2011, 12:12:16 AM »

Thanks Mattmayn,
that does answer the question.
we are a little unusual in how we provide services but basically there will be no extn-extn dialling between the two PABX's. Also the customer is having their own DDi E1 presented to our PABX which is then extended over the IPtrunks to them via our IP network. We won't be sharing directories or extension numbers so no need for a cluster. I'm happy now that I know.
Cheers
Chris

12

Mitel MiVoice Business/MCD/3300 / Clusters - Do I need them

« on: October 10, 2011, 11:03:03 PM »

All,
getting a little confused over the cluster issue.
I am configuring a remote CXiII for a customer that is going to use our MXE as a gateway to the PSTN. Having never done IP trunking before I followed the help sheets and got it all working. However I have some questions re clustering.
1. Can I configure IP networking without Clustering.
2. Why do I need CEID digits. (works fine with ARS digits pointing to the route).
3. Can I stop the Cluster ID being shown on the sets when there is a call between nodes.
Both PABX's are MCD 4.2
Thanks
Chris

13

Mitel MiVoice Business/MCD/3300 / 3300 & Tenor Quintum SIP Gateway

« on: September 26, 2011, 12:40:29 AM »

Has anyone been able to configure a quintum gateway (AS or AX) to work as SIP back to a 3300. Having trouble getting one to work at the moment. The 3300 is at MCD 4.2. the quintum will be within the private network.
I also have a MBG on the network if this would be easier as the interface to the quintum.
Cheers
Chris

14

Mitel MiVoice Business/MCD/3300 / Re: ata setups

« on: August 26, 2011, 01:35:21 AM »

I've used an ALGO 8180 on a remote site as a loud bell. we have 5312 handsets on the site, so i created a Generic SIP extension for the algo and added it to a couple of ring groups for the extensions that are on site. Works very well. we also connected an external 8 Ohm speaker to it and it's v loud.

Not sure, (and anyone feel free to correct if I'm wrong) but prior to enterprise license you couldn't do SIP unless you had specific 'SIP USER' licenses. I think that when you go to MCD any 'SIP USER' and 'IP DEVICE' licenses and get converted to enterprise licenses, because in MCD there are no 'SIP USER' licenses and 'Generic SIP' is now an option in 'Device Type' when you create a new user. I know that I had no SIP user licenses pre MCD and now i have a number of SIP devices purely because it is now included in one license.

Cheers
Chris

15

Mitel MiVoice Business/MCD/3300 / Re: 5314/5324 phone show "extension number" in the display panel

« on: August 15, 2011, 08:14:54 PM »

tried that and it works fine, probably going to be handy for some of our customers. But does anyone know of a way to get rid of the time and date from the display.
we have a number of extensions that are in different timezones so would like to rmove it and replace with either extension number or nothing at all.