Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Mitel ignoring DNS SRV priority

« on: February 26, 2019, 09:54:40 AM »

The servers do not respond to any pings. We figured it would be best because we were having call issues due to the back and forth and was recommended by the sip provider. Will lowering it have a better impact?

2

Mitel MiVoice Business/MCD/3300 / Re: Mitel ignoring DNS SRV priority

« on: February 26, 2019, 09:05:02 AM »

The weight is set in the SIP providers SRV record.

Primary has Priority 1 Weight 50
Backup has Priority 2 Weight 50

Non-authoritative answer:
_sip._udp.ny01-siptrunk-pai.megapathvoice.net   SRV service location:
          priority       = 2
          weight         = 50
          port           = 5060
          svr hostname   = lsancagb-siptrunk-pai.megapathvoice.net
_sip._udp.ny01-siptrunk-pai.megapathvoice.net   SRV service location:
          priority       = 1
          weight         = 50
          port           = 5060
          svr hostname   = nycmny83-siptrunk-pai.megapathvoice.net

lsancagb-siptrunk-pai.megapathvoice.net internet address = 67.103.60.53
nycmny83-siptrunk-pai.megapathvoice.net internet address = 72.244.209.53

DNS SRV REsiliency is set to 30

In this setup I should not be using the backup ever unless primary is lost. But I am still having it flip to the backup. SIP Provider recommended this resiliency setting. Should I try raising the resiliency even higher?

3

Mitel MiVoice Business/MCD/3300 / Mitel ignoring DNS SRV priority

« on: February 21, 2019, 01:47:32 PM »

We are using an internet based VOIP provider with a 3300 that we run through a Mitel Border Gateway and they have provided us with a DNS SRV record with a clearly defined priority 1 weight 50 and priority 2 weight 50 for a primary and backup server.

The issue that we are currently experiencing is that the even though the primary is not down it will flip back and forth between the primary and backup at random. At best this may be every hour or so, at worse its several times a minute. So far the only way we can stop this is to just force it directly to an A record but we lose redundancy with this method and isn't optimal.

Has anyone ran into this issue? Is there a setting that we are missing somewhere that is telling the Mitel system to treat these as a round robin?