MWI Cisco SPA 525G2 not lighting up

Status
Not open for further replies.

Andrew Byrd

Member
Feb 16, 2018
309
10
18
53
I have 3 spa525G2 that have been in use for over 6 months. Just recently, I moved the Fusionpbx application to a new server.. Ever since the move, MWI for ext 310, their shared voice mail ext, no longer works

In extension set up I set up MWI to 310@abn8.npusa.us That is the vm ext and the domain their on.

Not sure what else to check

any ideas?
 

Andrew Byrd

Member
Feb 16, 2018
309
10
18
53
I did find that MWI is working correctly on my Yealink T29 but not on the Cisco Spa 525G2 or the Cisco Spa 508G
 

Andrew Byrd

Member
Feb 16, 2018
309
10
18
53
Short term I just replaced the 525G2 with a yealink T29. Now MWI works. I will just not use 525G2's in production anymore and if I need the wifi feature (only reason I use the 525g2) I will use the Yealink T29 with a wifi adapter or use the Yealink T54W
 

Dast

Member
Nov 11, 2019
56
9
8
Just curious what system they were working with prior to switching to Fusionbpx?
In my limited experience, Cisco voip phones are a pain in the ass when it comes to SIP.
 

Andrew Byrd

Member
Feb 16, 2018
309
10
18
53
Thank you for your input on this. I moved an instance of Fusionpbx from one server to another Fusionpbx server. Cisco spa series are work horses. For the most part, I have learned how to make them play well with Fusionpbx/freeswitch. Moving forward I only sell and install Yealinks. They play well the best in my opinion. I have several clients that still use spa525g2 due to the WIFI and they do not have a way to get cat5 to that location. In that case, I am migrating them away from spa and replacing with Yealink T29 with a wifi dongle or a Yealink T54W.

The MWI was working fine on the previous Fusionpbx 4.5.11 server. After the move to a larger storage server, the MWI simply will not work on spa but will for Yealinks.
 
  • Like
Reactions: Dast
Status
Not open for further replies.