Dallas Latency / Potential Network Attack

[VOIPoTim]

My line 1 is registered, but line 2 is not. Also, outbound calling issue - after about 30-45 seconds, it cuts the call off and goes to fast busy. Related?

Likely, yes.

Go ahead and reboot if you're still seeing this and then update your ticket if it does not resolve it.

[dmbmar]

Rebooted at 8:40 MDT. No help. Line 1 does not register. Line 2 does. Ticket updated.

Also tested outbound call - fails at about 45 seconds - goes to fast busy. Inbound appears to be normal.

[VOIPoTim]

Rebooted at 8:40 MDT. No help. Line 1 does not register. Line 2 does. Ticket updated.

Also tested outbound call - fails at about 45 seconds - goes to fast busy. Inbound appears to be normal.

Reboot and try now (or wait until it re-provisions every hour). I think I see what happened with yours. The update changed your SIP ports to new default ones. We've restored all SIP ports to what they were before.

[dmbmar]

Will reboot shortly and update thread and ticket.

[dmbmar]

Will reboot shortly and update thread and ticket.

Update. After reboot, outbound calling issue appears to be resolved. However, only one line (line2) is registered. Half way home.