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

Pages: [1]
1
SIP On Mitel / Re: MPLS re-design
« on: August 12, 2019, 09:55:21 AM »
Yes currently on MPLS - smaller sites using 10MB lines all the way to 50MB.

2
SIP On Mitel / Re: MPLS re-design
« on: August 09, 2019, 12:04:43 PM »
Thanks for the relies people..let me verify a few more things for you.
For now most branches are pretty small, even the call center, all within 25 miles of each other.

3
SIP On Mitel / MPLS re-design
« on: August 08, 2019, 03:52:03 PM »
We are looking at moving to an ATT network on demand(layer 2) design from current MPLS. With that being said we are looking at how this will effect our current phone setup or a possible re-design.

25 branches with a 3300 on each premise.
3 MBGs being utilized, 2 head ends and 1 call center. (3 SIP trucks total i believe.)

Thinking ahead could the 3300's be possibly replaced or consolidated by anything at those 3 main MBG centers? With the new network design we are looking at a minimum of 1Gig speed per location.

Not too well versed in the phone system so forgive the lack of detail!

4
Mitel MiVoice Business/MCD/3300 / Re: Call quality/one way audio
« on: August 12, 2016, 01:12:21 PM »
It's going to be a network issue.
Odds are good that the QOS on the MPLS is not correct.

Ralph, If all the branch routers have the same QoS as well as the main MPLS router(all set at 40%) wouldn't I see packet drops in the service-policy if this was indeed a QoS issue? I can attach the policy stats for the policy if that helps.

5
Mitel MiVoice Business/MCD/3300 / Re: Call quality/one way audio
« on: August 12, 2016, 11:19:44 AM »

One thing, if you are prioritizing rtp over signaling and the pipe is full, sets will disconnect if their signaling "heartbeat" messages between the 3300 and the set is delayed for too long.

Thank you for the replies...since this has started a few weeks its hard to keep track of all the issues, exact dates, times, external/internal calls etc...apparently ATT was doing some construction on the line in one of the areas, the static issue has not been reported since, so at least for now we can rule that out.

The biggest complaint right now if one way audio, yesterday we had a person call our 1-888 number and dialed the extension in question. The person making the call could hear our employee but our employee could not hear her. The employee had the customer hang up and she called her back and the call went through fine.

I'm not too familiar about your comment regarding RTP and prioritizing, where could one look at that setup? As for looking at log files again I'm not too familiar with the MBG interface, there are so many log type to choose from!???


6
Mitel MiVoice Business/MCD/3300 / Call quality/one way audio
« on: August 11, 2016, 05:29:02 PM »
    Hi there...
    So the past few weeks we have had users complaining about calls getting disconnected, static,call quality etc. We are trying to pin point the issue weather it be network based or local(3300). We have 25+ locations serviced by 3 MBG's with each location with a 3300.

    In one particular location we have had the same 4 users complaining about calls getting disconnected. The call comes in fine to the secretary but once she transfers to the person it disconnects or cuts out after 30 secs or so. Also, direct calls to that branch experience the same cut off, static etc...now more offices are experiencing the same...its very sporadic to pin point or diagnose.

    We operate in a MPLS environment with a 50MB pipe back to our 3 Main locations with MBG's...all other locations vary in range from 3MB to 12MB. QOS is set up on each branch router at 40%.

    Anybody got any advise on where to start diagnosing further? We have engaged our phone service contractor but we want to make sure its not network based, we are not the phone guys!
    PS..we do have access to all the MBG's and controllers if that helps.

    Thanks in advance...
    nosing these issues, we are not phone guys

Pages: [1]