Hi all,

I have been with Snap UFB just over a year now and all in all I'm happy with the service.  When I signed up I elected to waive the offer of a Fritzbox and instead use my own hardware.  I run a Mikrotik RB751G-2HnD router and a ye olde Linksys PAP2T for VOIP duties.  This combo has worked flawlessly up until this week.

On Thursday I received a phone call from a cheerful Snap staff member asking me if I could enable remote access on my Fritzbox so they could push an update.  When I said I didn't have a Fritzbox they said they'd talk to their manager and call me back, which they did.  They then told me that the update pertained to migrating me from the "old" SIP server (123.255.8.255) to the "new" SIP server (connect1.plus.snap.net.nz), and should simply be a matter of updating the respective setting on my ATA device including adding a leading zero to the username (i.e. my phone number).  Simple?  Yeah nah.

My PAP2T keeps throwing an error "can't connect to login server" when trying to register with the "new" SIP server.  Switching back to the "old" SIP address (or in fact any other SIP server) works like a charm.  The aforementioned cheerful Snap staff member suggested checking my firewall to make sure the connection isn't being blocked, which it isn't.  As Snap don't officially support anything other than the Fritzbox the cheerful staff member then suggested he leave me to "play around" to see if I could get it to work.

I can't fathom for the life of me why this isn't working.  connect1.plus.snap.net.nz resolves to chcacme01.plus.snap.net.nz which resolves to 123.255.8.82.  I get no ping response from that address and from my perspective port 5060 is not open there either, so no wonder my PAP2T can't connect.  If I run a trace route to the two respective addresses this is what I see...

Firstly the "old" SIP address:

C:\Users\Administrator>tracert 123.255.8.255

Tracing route to 255.8.255.123.static.snap.net.nz [123.255.8.255]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router [192.168.88.1]
  2     8 ms     3 ms     3 ms  111-69-1-xxx.core.snap.net.nz [111.69.1.xxx]
  3     2 ms     2 ms     2 ms  32.54.69.111.static.snap.net.nz [111.69.54.32]
  4     2 ms     2 ms     9 ms  185.16.69.111.static.snap.net.nz [111.69.16.185]
  5     3 ms     1 ms     2 ms  184.16.69.111.static.snap.net.nz [111.69.16.184]
  6     2 ms     2 ms     2 ms  255.8.255.123.static.snap.net.nz [123.255.8.255]

Trace complete.

... as expected.  Then the "new" SIP address:

C:\Users\Administrator>tracert 123.255.8.82

Tracing route to connect1.plus.snap.net.nz [123.255.8.82]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  router [192.168.88.1]
  2     2 ms     7 ms     2 ms  111-69-1-xxx.core.snap.net.nz [111.69.1.xxx]
  3     2 ms     3 ms     3 ms  32.54.69.111.static.snap.net.nz [111.69.54.32]
  4     2 ms     4 ms     2 ms  116.53.69.111.static.snap.net.nz [111.69.53.116]
  5     2 ms     4 ms     2 ms  117.53.69.111.static.snap.net.nz [111.69.53.117]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

... and it keeps hopping to nowhere, forever.  Which could be normal, or could represent a routing problem.

Has anyone else out there had this issue?  Is there a kind Snap UFB user out there who could also check these traceroutes and see if theirs are any different?  Many thanks in advance...