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 - chewie

Pages: [1]
1
What was the problem for you guys?
Also how DO you properly wireshark with the desk phone?

I turned on port mirroring, plugged my laptop into the back of the phone on the PC port, started wireshark across that NIC, and then made a call and I'm not seeing it dump anything out about it.

2
No for all firewalls involved.
I had that thought as well.

3
It's funny because we had a Mitel Engineer on the phone for like 2 hours today looking at it.
It should be working but isn't and the engineer is now trying to replicate it in his own lab to troubleshoot.

4
I've combed the logs and I am not seeing a darn lick of VOIP traffic being dropped on either end.
It really is crazy.

The only thing I can see is that there is some complaints on this end about irregular voip traffic coming from the mitel 3300 here to the other site's 3300, but no corresponding log entry on the other side.

I do see, whenever I make a test call to the other site, in their firewall log, alerts about voip-apps sip, coming from the micollab and MBG systems we have setup along with this 3300, with a destination to their 3300, port 5060 and UDP, but it isn't saying it's dropping it, just alerting.  Plus those IP's aren't matching the IP's of the actual call system here...unless the new 3300 system setup talks through MiCollab and MBG? I mean, did that change?

5
Well, not sure what the data sharing was supposed to do, but the directory only has local #s.

So how in the world does mitel know that when I dial an extension in another site, that it translates it to that person's #?
I can't figure out the call flow from how it's presented...

If SDS sharing is broken due to the version differences your directory may not be getting updated. Sometimes if we use a speed call or a main ACD number that info isn't in the directory either so we have to put it in. I would do a test and add one of the numbers not working in to your Telephone Directory. If that works you can export that entry as a .csv and use excel to put the rest of the info in, then upload the new info.

The SDS sharing lets Node A know that extension 3456 is on Node B when the extension is dialed from Node A. However, if there is no other information it won't be able to say who it is calling. Typically the Telephone Directory is shared, but if that part is broken - or the nodes need re-synced that could all be in play as a potential issue.

Does data sharing have to be enabled for SDS to be working properly?
It was on the old system, not in the new, and I have no idea why it was before and why it wouldn't be now.

6
Before I do that, quick update.
It shows the extension # and then IP TRUNKS after it, so not just IP TRUNKS.
So part of the callerID is coming in.

7
Well, not sure what the data sharing was supposed to do, but the directory only has local #s.

So how in the world does mitel know that when I dial an extension in another site, that it translates it to that person's #?
I can't figure out the call flow from how it's presented...

8
ZuluAlpha... you may be on to something.
All of the entries in the directory here are showing this site's info only.
I saw on the old system, data sharing between this and the other site in question was enabled. 

What does that data sharing actually do?

9
Hmm.

So you're saying Trunk Label controls what the other site would see for callerID?

I just looked @ the old system, and it was set to IP Trunks as well.  So not sure why it wouldn't have shown that way before hand then.

If there is no label there, what do they see? Nothing? Or would they see an extension or a name?

10
Hi Sunspark.

Yes, in trunk attributes we have two trunks I see:

One labled IP Trunks, the other IP Trunks2.

Are you saying those should be blank or something else?

11
Mitel MiVoice Business/MCD/3300 / One way audio issue with a single site
« on: December 04, 2017, 11:05:00 AM »
Hi all.  At my wits end diagnosing this one thus far...

We are running a Mitel 3300 here at this site, on version 44.0.1.26. The other site in question runs a 3300 on 40.2.0.16.

When we call that site by using their 4 digit extension, we can hear them, but they can't hear us.
If we dial their full DID, they can hear us, and we can hear them.

Normally, I'd say, well this is a networking issue, as the sites are connected via VPN and thus this would have to be a firewall and/or routing issue....except...it sure as heck does not appear to be.
They are running their site off a Model 200 Dell NSA, and we are using a 4600 series, so my thoughts have somewhat strayed to thinking maybe there is a VOIP setting we need to turn on there, but... previoulsy, we ran another 3300 from another vendor with a slightly older version of the software (same as the other site), and two way audio worked just fine.

The only changes have been to the 3300 box itself (different box, different vendor), the software it runs (new version on this end), and a VLAN change (We implemented the VLAN for voice at the same time).  Now, the firewalls I can verify all have the correct setup for in and out traffic, where it's allowing what, and they all know about each other's networks including our new VLAN.  We have two other sites with 3300's that talk to us internally via the same exact VPN channels with the same settings with 0 issues. It's only this one site.

Now, my boss mentioned to me that there was an issue like this when the last box was first implemented, and there was a CoS setting that had to be tweaked here for it to work.  We haven't been able to find our notes (it was so long ago) and I have been pouring over everything I can to figure it out.

Settings between systems seems to match up. The only glaring difference was that in our LAN Policy (QoS) settings, Voice Signalling is set to 24, and on the old system it was 26, and on all the other sites it's 26. But the other sites work just fine, and the DHCP settings for the phones being handed out have the correct 26 setting for the same voice signalling setting. So...still not sure.

But..that being said, any ideas here? I am considering trying to race the call via the maintenance interface, but not sure how to do that, and our vendor keeps pointing us to our network settings. While it still could be something obscure, I'd still like to rule out the 3300 itself and see if there is anything offhand anyone can think about to try that won't require a reboot per say (as that would have to be done after hours, and noone will be at that site then).

I also tried placing the call to the site on hold and picked it back up, as I read that someone had that kind of issue that alluded to being a 3300 issue and not networking.

But, out of ideas at the moment. I went down the networking path a dozen times now, and everything says both sites can talk between our VLAN and theirs, etc. And again, it's the only site with an issue as such.

Appreciate any insight.

12
Hi all.  We have a Mitel 3300 running  44.0.1.26.

Running into another issue, which we are being told is due to system versions/incompatabilities between them.
One of our sites, which uses site to site VOIP connectivity from here to there and vice versa, shows anyone who calls from here to there as 'IP TRunks' for caller ID.

Everything I've read says that if callerID isn't available, then it will default to the description/name label in our system...it worked on our older system just fine, and only happened when we upgraded this site to the version mentioned above.

The other site in question is running a 3300 at 40.1.1.10 .  However we have two other sites with 3300's as well, and at least one of them runs 40.2.0.16 but their caller ID shows us correctly (AFAIK). So far it's just this one site saying it shows that way.

What would I be looking for in this case?  Is there something I need to turn off or on on this end, and likewise the other end, for callerID to be displaying properly? It displays correctly calling the other sites, and also external lines from here, and internal lines from here (desk to desk) work as well.

Appreciate any help.

13
Hi all.

So, just as an update, our vendor states Mitel has a solution called Twinning. I know how to set that up now, HOWEVER it's not how the old system was setup.

On the old system, you'd simply activate call forwarding in the phone settings of the phones (5330 and 5330e) and then when someone called your DID or ext (regardless if an internal or external call origin), it would ring the forwarded line, and then dump back to internal voice mail.  This was with call forwarding all, same as I am trying now (the other call forward options yield the same behavior).

Now, I've been comparing the current CoS to the old system's CoS, settings, etc, and for the life of me, cannot figure out how in the world that would have worked before. Currently, the forwarded line picks up for voicemail, which would make sense since the call would get handed off to them. 

So, let me ask...how would that have been controlled, as the old system wasn't configured with hotdesking what soever.  Twinning is too advanced to roll out right now for folks, so we want to stick to basics.

Seems like it should be a timer, but for the life of me, nothing I've tried works.  Here are the current timer settings though for the CoS for our phone CoS (the ones the users are told by the mitel system to use):

Code: [Select]
Call Forwarding/Rerouting
Call Forward - Delay 0
Call Forward No Answer Timer 22
Call Forward Override No
Call Forwarding (External Destination) Yes
Call Forwarding (Internal Destination) Yes
Call Forwarding Accept Yes
Call Reroute after CFFM to Busy Destination Yes
Call Forwarding Reminder Ring (CFFM and CFIAH only) No
Disable Call Reroute Chaining On Diversion No
Follow Reroute on Disabled Forwarding No
Group Call Forward Follow Me Accept Yes
Group Call Forward Follow Me Allow Yes
Third Party Call Forward Follow Me Accept Yes
Third Party Call Forward Follow Me Allow Yes
Use Held Party Device for Call Re-routing Yes

Code: [Select]
Call Hold Timer 180
Code: [Select]

Ringing
Delay Ring Timer 10
No Answer Recall Timer 30
Ringing Line Select Yes
Ringing Timer 180

On the old system, No Answer Recall timer was set to 125, and call forward no answer timer was set to 13. I tried those settings and it still didn't work.
It's almost like the old system shouldn't have done what it did and the new system 'fixed' it.

It would be nice to know where this all needs to be applied and what needs to be applied as from what I can see it SHOULD work, but doesn't.

Does this need to also be somewhere on the CoS for PRI, and or IP trunks?


14
Hi all, new to the forum and new to administrating the mitel PBX system.

Trying to figure out how to properly allow a call to be forwarded to external mobile (if user not available lets say, or if they manually enable it), but have it fall back to internal voice mail if no-one picks up there?

It almost seems like a class of service option, and perhaps a # of rings, but the documentation is not that clear and I'm having trouble finding the right option(s) to do this.  I'm more used to FreePBX/Asterisk and Cisco CCM, so struggling a little bit.

Did a bunch of searching but not getting much info, so any help is greatly appreciated :)

Pages: [1]