@dbeato said in Anyone ever return a server to Dell?:

Don't accept the shipment and let it get back to Dell. That is the only way.

My rep finally got back to me and told me to do the same thing. I just wish there was a way to stop the shipment before it reaches my door. I tried to put a call in to Mach1 but couldn't get through to anyone.

Is your Synology joined to the domain? If so, do the users trying to access have proper permissions? Also, if joined to the domain, confirm that it is still connected. Occasionally the domain connection can become disrupted for various reasons.

If you go to a command prompt and type "net use" do you already have an existing connection established with the Synology using a different user account?

I don't think this would be it since you can access from the ip address but what version of SMB do you have set for your minimum and maximum on the Synology?

@notverypunny - I am not sure yet. Dell never seems to use FedEx or UPS when shipping servers. They are using Mach1 Global which is a first for me.

@gotwf said in Anyone ever return a server to Dell?:

@syko24 I stopped doing business w/Dell circa 2004/5. I spec'd out a box for a client and had the order held because the client wanted to pay direct rather than thru me. When they did, the sales rep tried up selling them on different hardware and RHEL (went so far as to tell them Debian was NOT Linux). Also went so far as to bad mouth me to the point client confronted me about it before pulling the trigger. Fortunately I had a pretty good relationship w/this client and I prevailed. Hate to have thought what might have ensued otherwise. Lots of big operators swear by them but, since you asked, there's my Dell horror story. New here w/zero rep but I'd keep the xByte.

Caveat emptor. Good luck.

@gotwf - Agreed, I would prefer to keep xByte as they are just a much better run operation. However, if Dell is going to pull some crap and try to charge a 15% restocking fee then I may need to consider keeping it and sending back the xByte server. I have emails out to both companies trying to see what my options are.

So long story short, I purchased a server from Dell about a month ago and of course the order was delayed multiple times. I finally ended up ordering a server from xByte. The xByte server shipped within 24 hours and I had requested a cancellation from Dell. I go to check my email today and go figure Dell just shipped my server. Bottom line, I need to return one of them when I receive them. Has anyone had to return a server to Dell or xByte and were there any fees associated with the return? Honestly I'd rather give the money to xByte as they pushed the order out immediately and they just handle orders and support so much better than Dell does.

@Skratch08 said in FreePBX Random Trunk Disconnect:

I was having similar issues with this the week of 04/22/2020, with the chicago3.voip.ms server. This was shortly after they added new servers in Chicago. I switched everything to chicago7.voip.ms and have had no issues since.

@Skratch08 - Thanks for the response. I typically use Chicago2 for all my installs so that would make sense if that particular server address was having issues. I'll try a different one and see if there is any difference.

Thanks again!

I noticed this on one of the client's systems. Not sure why voip.ms is not accepting the credentials. I went in and opened my trunk settings, clicked submit, and apply settings and it reconnected.

[2020-06-03 12:40:28] NOTICE[8863] chan_sip.c: Peer 'voipms' is now UNREACHABLE! Last qualify: 1
[2020-06-03 12:40:59] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #2)
[2020-06-03 12:41:19] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #3)
[2020-06-03 12:41:39] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #4)
[2020-06-03 12:41:59] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #5)
[2020-06-03 12:42:19] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #6)
[2020-06-03 12:42:39] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #7)
[2020-06-03 12:42:59] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #8)
[2020-06-03 12:43:19] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #9)
[2020-06-03 12:43:39] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #10)
[2020-06-03 12:43:59] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #11)
[2020-06-03 12:44:20] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #12)
[2020-06-03 12:44:40] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #13)
[2020-06-03 12:45:00] NOTICE[8863] chan_sip.c: -- Registration for 'xxxxxxx@chicago2.voip.ms' timed out, trying again (Attempt #14)
[2020-06-03 12:45:00] WARNING[8863] chan_sip.c: Forbidden - wrong password on authentication for REGISTER for 'xxxxxxx' to 'chicago2.voip.ms'

Has anyone else had random disconnects from Voip.ms this week or last? I have had 6 different FreePBX servers randomly disconnect from Voip.ms and not reconnect without manually pressing Submit and Apply Settings.

The dashboard shows the trunk as connected but the Reports > Asterisk Info > Chan_Sip Registry > State show as No Authentication.

All my servers are hosted on Vultr using Chan_Sip for the trunk settings. Below are my settings and I am wondering should NAT be set to NO if hosted on Vultr? Thanks

canreinvite=nonat
nat=yes
context=from-trunk
host=chicago2.voip.ms
username=Username
fromuser=Username
secret=Secret
type=peer
disallow=all
allow=ulaw
trustrpid=yes
sendrpid=yes
insecure=invite
qualify=yes

I've had a couple clients use the GrandStream GS Wave softphone on their iphones. It's free and can run in the background on iOS.

@Dashrender - I haven't used Skyetel yet but do they have an inbound setting like voip.ms does? On voip.ms there is the device type under inbound settings - "IP PBX Server, Asterisk, or Softswitch" or "ATA device, IP Phone or Softphone".

@JaredBusch said in Multicast Paging Server:

ok back.

The problem with option 2 is that is it only on the phones. That is also the benefit since it uses no SIP.

Third option is a device to be a multicast server. The Snom PA-1 is supposed to do this. I have never tested that. I keep meaning to, but I have not had one spare to setup.

You need to use option three when you have multiple sites because, as noted previously, you don't multicast over the internet (yes it can be done, let's not go there right now).

So if you need to page to site 1 and site 2 at the same time, then you can make a page group to a device registered at each site (snom or the like) that then does the multicast locally.

@JaredBusch - So basically the paging server would be a waste of money if only using at a single site? It only comes into play when you need to page at a second location.

If doing multicast at a single site from just the phones, is there a device limit or a point at which you can cause issues on the network? This site is 35 phones so I don't see that being the case but just out of curiosity.

I am in the process of setting up a couple paging groups. I know that FreePBX limits the size of your page group to about 40 devices. My Vultr cloud instance craps out at about 9 devices. If I want to include all phones in the page group I see it is recommended to use multicast as the alternative. Some recommendations are to use a multicast paging server and others show you can just do it direct on the phones. Does the multicast server come into play after a certain amount of devices or is that if you are paging other locations like a branch office?

Thanks

@JaredBusch said in GrandStream phones with FreePBX:

I don’t have one of them.

But I have multiple phone systems to test with if you want.

We could set one up to my PBX and let me watch the logs and such.

Thanks @JaredBusch for the offer. So I know this should have been more obvious but there was a SonicWall router in place at this site. The reason I didn't think much of it was because about half the phones were working properly and the other half were not. I was thinking the issue was something with the local RTP being set at 5004 on the GrandStreams.

I swapped out the SonicWall with an EdgeRouter but that still did not fix the issue. I rebooted the isp's modem and rebooted the edgerouter. I factory reset all the phones and they all connected. I tested that all could access extension calls and make outbound calls. For now I am assuming the SonicWall was the culprit but tomorrow will tell.

If I run into this issue again I may take you up on your offer. Thanks again!!

Just to update this, I am using FreePBX 15 Asterisk 16. Started off using PJSip as the default and then switched to ChanSip. All extensions connected on ChanSip but extension to extension on some phones is still not working.

Just some more info:

Some phone connect alright but then seem to lose extension to extension audio. This is what lead me to the RTP settings on the GrandStream.

The phones that do not connect are pulling their lines settings and blf settings correctly from the FreePBX so I know it is connecting or sort of.

Has anyone deployed the GXP2170 and GXP2135 with FreePBX. I am having a hell of a time getting them to connect to my instance on Vultr. I noticed on the GrandStream the local rtp port is 5004. Do I need to change with to 10000?

I deployed using the EndPoint Manager so I assumed the settings would be good to go but apparently something is not right.

Appreciate any feedback.

Thanks

@zachary715 - Again thank you for the the info. My concern is that the users will have to constantly keep re-authenticating their Outlook on their work desktops which would be a pain. One laptop I setup was asking for credentials 15 minutes after I set it up. I was nervous thinking that all the systems were going to do this but I think it was isolated to that one system.

@zachary715 - So when I setup users with MFA enabled and connect them to Outlook 2019 (365), I assume you cannot use the app password with Modern Auth enabled. What is the best method for connecting Outlook without having to constantly enter a sms code or using the authenticator?

@zachary715 - I appreciate the very detailed response. Definitely answers a lot of the questions and issues I ran into today.

One thing I noticed is that the internal users in the office logging in on their computers were forced to enter cell phone numbers upon their initial login. The external service techs that only use their cellphones were not given this option upon their initial sign in to email. The techs were only given the option to use MS Authenticator which caused a lot of confusion. While I know the authenticator app is more secure, it would have been nice if they had been prompted to add their cell phones numbers in order to provide 2fa over sms. Really without being in front of a desktop during your initial user setup, setting up the authenticator from a cell phone is a little bit of a nightmare for a typical user. I know they can hop back and forth between apps to copy and paste but these are not tech savy users. Ultimately I ended up having to set everyone's devices up for them which was a pain. I did find out after the fact that I can enable phone as one of the MFA options.

I just felt like the average user would need a lot of hand holding to get this setup. I was struggling mostly because I was unaware that this was the default setup on new accounts now.