Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Disabling 802.1x and other settings globely

« on: December 15, 2014, 09:22:49 AM »

Hi,

yes but this does not answer the question of disabling 802.1x, Because 802.1x is enabled on the phones by default but no user name is set, they will hang trying to authenticate on 802.1x and never fail-over to MAB.  The only way you can do a MAB is to change the priority of authentication on the switch from 802.1x first followed by MAB to try MAB first. This causes another host of issues as device you want to do 802.1x will authenticate with MAB.

you can also try LLDP/CDP to bypass authentication for the voice vlan, but again once you actually try this you start causing issues for other devices that might want to use LLDP/CDP

Both possible but both feel like a bit of a "hack" to get it working.

2

Non-Mitel Chatter / Re: Register Mitel hand set to Sonus SBC (SIP)

« on: December 03, 2014, 11:01:17 AM »

Sorry the error I see is

User-Agent:Mitel-5312-SIP-Phone 05.00.00.18 08000F4D54EF
Authorization: Digest username="(null)", realm="(null)", nonce="547f336935343765656431382D3361612D336666", uri="sip:149.155.224.30", response="a0a1f33c5a550133665b88616ad0f8c5", opaque="", algorithm=MD5
Supported:path,outbound,eventlist,gruu
Max-Forwards:70
Content-Length:0

3

Non-Mitel Chatter / Register Mitel hand set to Sonus SBC (SIP)

« on: December 03, 2014, 07:58:41 AM »

Hi,

has any one ever successful registers a mitel 5312 or similar model to a SONUS SBC?

we have at one branch site only a sonus SBC1000 and I would like to register a mitel hand set to it in sip mode.

I can get in OK and configure the mitel sip user name and password. and have followed the SIP configuration on the Sonus, but in the sonus logs i see  "username="null" password="null"

If any one has set some thing like this UP I would be interested to hear how

cheers

4

Mitel MiVoice Business/MCD/3300 / Re: Disabling 802.1x and other settings globely

« on: December 03, 2014, 07:50:08 AM »

HI,

no never found a way to do this with out manually doing each phone.

5

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 24, 2014, 11:22:59 AM »

Try this, although it may effect the outbound, too:

Assoc. Dir. Numbers

Add

Dir. Num. 1234

CPN Sub.

Assoc. Num. 9999

Then make a test call both internal and external.

I tried this but it has not made any difference

I set ext 4136 as the Dir number, and 1368 as the Assoc num.

then called 1394 from the 4136 handset expecting it to show as 1368 but I still see it as 4368.

6

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 24, 2014, 11:09:09 AM »

To hid a directory name you can do add a '!' in front of the name.   So "Ralph" becomes "!Ralph".   There's no way to search for a "!"

Ralph

That worked perfect thank you

7

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 23, 2014, 04:48:54 AM »

Hi,

Sorry for the delay, we are running a version of 5 will have to check later. I will also check out your posts and see if I can get it to work.

And don't suppose you can tell me how to hide a number from the directory, so should some one search for a user it does not show. Seems as soon as I add a user they are searchable in the directory and I not sure how to stop that?

Cheers

8

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 15, 2014, 10:24:46 AM »

One further Questions, it is possible to do calling ID substantiation between extensions on the same Mitel switch? So if EXT 1234 calls 5678 it looks like it comes from 9999.

Thank you

9

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 12, 2014, 05:03:31 AM »

Hi that worked perfectly thank you very much

10

Mitel MiVoice Business/MCD/3300 / Re: Blocking Calling Number ID

« on: September 11, 2014, 09:31:47 AM »

Hi,

Well the set up is

1 X ISDN + 1 X Sip trunk from provided terminate on to a Sonus SBC.

this in turn has one ISDN30 to Mitel (this ISDN use to go out direct to supplier now the Sonus sits in between) and one sip to Lync.

This is what I see,

When I make a call from Mitel system to another Mitel system then the caller is displayed on the hand set.
When I am a call out from the Mitel system to the Lync or external number, on the Sonus logs I see the callingID as jsut "-"
When I make a call from External/Lync to Mitel i see on the Sonus logs both a calling and called ID sent out the ISDN to the Mitel, but I don't see this on the handset.

What I want is when a mitel user calls a Lync user or Lync calls Mitel, either system shows the extension it is coming from. But on the Mitel system it seems apart from mitel to mitle calls every thing comming in or out the ISDN has its calling ID stripped. So I jsut want the Mitel to always display/send the calling ID and I will block it as needed on the Sonus.

11

Mitel MiVoice Business/MCD/3300 / Blocking Calling Number ID

« on: September 11, 2014, 07:31:50 AM »

Hi,

I would like to know the different ways you can block the calling number when sending calls out an ISDN link.

On our system it seems to be set so that it strips the calling number out when sending calls out the ISDN line to external numbers, but I want it to send the number as we now have a SBC that links our phone systems together and I want to be able to control the visibility of the calling number on this system rather than the mitel.

Can any one tell me the various places this can get stripped? it seems to be at a globable level. I saw setting in the COS, but I don't see any of these applied from the assignments of clinets and users.

Thank you

12

Mitel MiVoice Business/MCD/3300 / Re: Disabling 802.1x and other settings globely

« on: January 29, 2014, 07:27:44 AM »

So what files can be downloaded to a phone when it boots from TFTP, are there no config files like the one posted above?

It seems crazy that should a company want to deploy port based authentication on there network the only option is to manually go in to the menu of each phone and disable 802.1x!

Surely if a phone is currently connected to the network and the ICP, there should be some way to remotely manage the settings? do the phones have an built in web server/portal to allow management?

2 sites, 50 buildings, high bio-containment, doing it manually is a nasty job.

13

Mitel MiVoice Business/MCD/3300 / Re: Disabling 802.1x and other settings globely

« on: January 28, 2014, 03:24:59 PM »

That depends for security all ports have to have 802.1x enabled.

now if the case is that a PC is attached then it can authenticate and allow the phone on by proxy to the voice network.

or if 802.1x is disabled on the phone then I can allow on to the voice vlan via mac authentication bypass (authorised base on mac address)

however if authentication is enabled on the port then even if i explicitly allow the phone vlan with out authentication because it is active at a port level it will request the phones credentials.  Sadly this stops the phone booting as by default 802.1x is enabled, it just hangs asking for a user name and password and does not seem to time out.

So that's the issue, even if you don't want to use port security you still have to disable it for it to work for you other devices, or put in a lot of extra config and rules.

I wont be sorry to see the back of our mitle system.

14

Mitel MiVoice Business/MCD/3300 / Disabling 802.1x and other settings globely

« on: January 28, 2014, 11:25:21 AM »

Hi,

Quite new to mitel and actually a network engineer so all a bit new to me.

I am currently implementing 802.1x authentication on our network, but an issue I have is that the mitel 52xx and 53xx phones by default have 802.1x enabled ,but no credentials. This means they simply hang and never can access the network unless some one manually either enters  come credentials or disables 802.1x on the phone.

I want to know if it is possible to download a config file to the phone during boot to either set up or disable this setting.

I did see some thing about phone configuration files which have this in them

[NETWORK1]
Enable = 1
SIP_Outbound_Proxy =
SSID = SIP
Enable_DHCP = 1
Address = 0.0.0.0
Netmask = 0.0.0.0
Gateway = 0.0.0.0
DNS1 = 0.0.0.0
DNS2 = 0.0.0.0
Security = 2
WEP_Bits = 0
Default_WEP_Key = 1
WEP_Key1 =
WEP_Key2 =
WEP_Key3 =
WEP_Key4 =
Post_Authentication_Mode = 0
8021X_Name =
8021X_Password =
WPA_PSK_PassPhrase = password
WPA_PSK_Key =
Use_WPA_PSK_Key_Hex_Mode = 0
Proactive_Key_Caching = 1
PMK_LifeTime = 43200
PMK_Max_Count = 32
DiffServ_Signal = 46
DiffServ_Media = 46
WMM = 1
Jitter_Buffer_Size = 60
Payload_Type = 8,18,0
Multiframe = 2,2,2

but I think this is well out of date, any ideas how to do this? I am running a 3300 controller.