|
|
|
richms: I had no issues with it on a managed sipira ATA from a US based VoIP provider
using the FXO taking in a NZ phoneline with CID activated however..
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Its pretty easy to configure FritzBox to work with spark. When I moved from Orcon to Spark, as a test I did configured FritzBox it and worked fine with Spark.
Cant remember exactly, but I think under network options instead of Orcon Provider, selected other ISP, in username password type the details (you can get it from Spark) and set it to use VLAN 10.
That's it. No other configuration required.
novice1981:
Its pretty easy to configure FritzBox to work with spark. When I moved from Orcon to Spark, as a test I did configured FritzBox it and worked fine with Spark.
Cant remember exactly, but I think under network options instead of Orcon Provider, selected other ISP, in username password type the details (you can get it from Spark) and set it to use VLAN 10.
That's it. No other configuration required.
My transfer to Spark went through this morning at 6am. Tested the Fritz and it appeared to be working fine so left for work. Half an hour later, my wife called me saying internet wasn't working, so I figured it must have still been on 2degrees when I checked it and that it had now cutover with the Fritz incorrectly configured. Turned out though there was a general network outage in my area that happened right after the transfer! But all back up now and working good as gold.
Thanks for your input everyone.
steve98:
novice1981:
Its pretty easy to configure FritzBox to work with spark. When I moved from Orcon to Spark, as a test I did configured FritzBox it and worked fine with Spark.
Cant remember exactly, but I think under network options instead of Orcon Provider, selected other ISP, in username password type the details (you can get it from Spark) and set it to use VLAN 10.
That's it. No other configuration required.
My transfer to Spark went through this morning at 6am. Tested the Fritz and it appeared to be working fine so left for work. Half an hour later, my wife called me saying internet wasn't working, so I figured it must have still been on 2degrees when I checked it and that it had now cutover with the Fritz incorrectly configured. Turned out though there was a general network outage in my area that happened right after the transfer! But all back up now and working good as gold.
Thanks for your input everyone.
Glad to hear your order went all through perfectly :)
Checking logs, looks like changeover happened at 5.56AM this morning, you were using your full snap login details until the outage as noted after 6.58AM.
As of 1.12PM, looks like you have reconfigured to spark username as part of the trouble shooting process and back all online :)
As we use port authentication long as you have a username and a password, it will be fine!
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:steve98:novice1981:Its pretty easy to configure FritzBox to work with spark. When I moved from Orcon to Spark, as a test I did configured FritzBox it and worked fine with Spark.
Cant remember exactly, but I think under network options instead of Orcon Provider, selected other ISP, in username password type the details (you can get it from Spark) and set it to use VLAN 10.
That's it. No other configuration required.
My transfer to Spark went through this morning at 6am. Tested the Fritz and it appeared to be working fine so left for work. Half an hour later, my wife called me saying internet wasn't working, so I figured it must have still been on 2degrees when I checked it and that it had now cutover with the Fritz incorrectly configured. Turned out though there was a general network outage in my area that happened right after the transfer! But all back up now and working good as gold.
Thanks for your input everyone.
Glad to hear your order went all through perfectly :)
Checking logs, looks like changeover happened at 5.56AM this morning, you were using your full snap login details until the outage as noted after 6.58AM.
As of 1.12PM, looks like you have reconfigured to spark username as part of the trouble shooting process and back all online :)
As we use port authentication long as you have a username and a password, it will be fine!
|
|
|