Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - 127.0.0.1

Pages: [1] 2 3
1
Unfortunately at this site, with the low number of handsets, they are using static IP assignment. It turns out the user there who had been given instructions on the correct IP address to program had fat-fingered the gateway IP (set it as 10.8.253.0 rather than 10.8.0.253).

Once this was rectified it is working now correctly. The blame on the codec by the ISP appears to have been a red herring.

I really hate these remote deployments for just these things that crop up, since there's no way to configure the Mitel phones via HTTP or Telnet unless they are in SIP mode. Hopefully there won't be too many more of these.

Thanks, everyone, for your assistance :)
Uhhgg... Statically assigned... I once had a 3300 certification instructor THROW A 5340 ACROSS THE ROOM when someone suggested doing this in class... One of the biggest, and most sensible, rants I have heard seen.

Props to the person who can guess this instructor... :)

Anyway, glad you figured it out.


A few years late but... I'm going with (the legend) Mike Smolka

2
Sounds like a station callback.  Just complete the callback by having the dialed party answer it.  MWI can be set from places other than voicemail.

3
Mitel MiVoice Business/MCD/3300 / Re: Remote Call Forwarding
« on: June 02, 2014, 04:58:00 PM »
UCA app on mobile phone to manage EHDU would be slick IF you have the licensing.

4
Mitel Software Applications / Re: SIP Trunking
« on: May 28, 2014, 04:36:08 PM »
Sweet!  It's BEER:30

5
Mitel Software Applications / Re: SIP Trunking
« on: May 28, 2014, 04:29:09 PM »
OK good, so back to tcpdump then.  Get a trace and see where the RTP is streaming to/from.

6
If you have NuPoint with Call Director you could intercept the digits in the PBX and send them to a call flow containing a restriction schedule

7
Mitel Software Applications / Re: SIP Trunking
« on: May 23, 2014, 10:55:34 AM »
Make sure the MBG blade network profile is set to server-gateway, and that the set-side IP and ICP-side IP are set properly.


^^^ What about this?  Server-only will set both ICP-side and set-side IP to the ICP.  Try overriding the set-side to the public IP. 

8
Mitel Software Applications / Re: SIP Trunking
« on: May 22, 2014, 11:43:40 PM »
This is bigger than SIP if TW has issues on IC calls.  A couple of thoughts.


Is MBG part of MAS?
Does MAS host NP as well or are you using embedded?
If VM is not on same MSL as MBG, is the VM, regardless of type in the same subnet as eth0 on MBG?


Make sure the MBG blade network profile is set to server-gateway, and that the set-side IP and ICP-side IP are set properly.


If you didn't, when you do your tcpdump from MBG's MSL, use '-i any' to capture on both eth0 & eth1 at once.  Your trace will show the big picture.

9
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 22, 2014, 12:53:26 AM »
A few unsolicited thoughts here.  Switch where you can, route where you must.  Do you really need to route between floors?  Flattening the voice subnets into a larger broadcast domain (drop a mask bit or two) and then just straight trunking between floors would actually be more efficient.  Layer 2 is always faster than layer 3.  It's science.

Is the controller in the .20 or .21 subnet?  Can you just kill the helper and turn on DHCP in the controller for a minute and just get a test?  Per RFC, DHCP only refreshes at T1 and T2, which are 1/2 and 7/8 of the way through a lease duration.  I doubt it will cause any interruption if you bang this out quickly.


Sent from my iPad using Tapatalk

10
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 21, 2014, 11:15:24 PM »
OK, I haven't seen a diagram yet, so here's Visio 0.1....  Is this close?  If so, where is your layer 3 happening?  In the firewall?

phone1---{sw1.vlan1001}---{fw}---{sw2.vlan1001}---phone2
         { 10.61.20.0 }    |     { 10.61.21.0 }
                           |
                          DHCP.192.168.0.2
                           |
                           |_scopeA.10.61.20.0
                           |_scopeB.10.61.21.0


11
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 21, 2014, 11:02:18 PM »
The two subnets do have different VLAN ID's, right?  1001 and 100_?

12
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 21, 2014, 07:11:46 PM »

2 scopes with one pool each
  • How many subnet mask bits are you using?  /24?  Something else?
  • What do the scopes look like?  Maybe a screen shot of your scopes expanded?
    Scope A
    --lease range = w.w.w.w thru x.x.x.x
    Scope B
    --lease range = y.y.y.y thru z.z.z.z
  • Previously you mentioned 130 phones.  Are there more?
  • You confirmed a single VLAN for all voice devices and that it extends between floors.  This makes makes a single broadcast domain and each scope would be reachable by either floor.  One DHCP server would be fine.
If the lease ranges overlap you can run into DHCP offer issues where scope B will offer an in-use address already leased by scope A, or vice-versa.  If this is occurring, then when the phone receives the offer it will immediately ARP for the address to see if another device owns it.  Actually, this happens every time an offer is received, but it should never receive a reply to this ARP request in a clean network.  If it does, then it declines the offer and broadcasts another DHCP discovery packet.  Since the offering scope did not lease it successfully, it re-offers the same address.  Rinse and repeat.  The wireshark capture will reveal this.


^^^^^^^

13
Mitel MiVoice Business/MCD/3300 / Re: Mitel MCD 7.0 Enhancements
« on: May 21, 2014, 10:23:50 AM »
I'm being a bit thick here, will the DDI improvements be like a 5000, i.e just match a ddi number to a destination? or still rule based as it is in SIP?


Yep, just like the Axxess/5000 call routing tables where you define the DID==>Destination pairing.  It requires setting an option in the trunk attributes otherwise the trunk follows the traditional routing options.

14
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 21, 2014, 10:20:09 AM »

2 scopes with one pool each
  • How many subnet mask bits are you using?  /24?  Something else?
  • What do the scopes look like?  Maybe a screen shot of your scopes expanded?
    Scope A
    --lease range = w.w.w.w thru x.x.x.x
    Scope B
    --lease range = y.y.y.y thru z.z.z.z
  • Previously you mentioned 130 phones.  Are there more?
  • You confirmed a single VLAN for all voice devices and that it extends between floors.  This makes makes a single broadcast domain and each scope would be reachable by either floor.  One DHCP server would be fine.
If the lease ranges overlap you can run into DHCP offer issues where scope B will offer an in-use address already leased by scope A, or vice-versa.  If this is occurring, then when the phone receives the offer it will immediately ARP for the address to see if another device owns it.  Actually, this happens every time an offer is received, but it should never receive a reply to this ARP request in a clean network.  If it does, then it declines the offer and broadcasts another DHCP discovery packet.  Since the offering scope did not lease it successfully, it re-offers the same address.  Rinse and repeat.  The wireshark capture will reveal this.

15
Mitel MiVoice Business/MCD/3300 / Re: Interminent DHCP issues
« on: May 21, 2014, 12:30:28 AM »
Different floors in the same voice vlan, right?  So you have one scope with two pools or two separate scopes with one pool each? 


Sent from my iPad using Tapatalk

Pages: [1] 2 3