Something stuck? No Vpanel or inbound calls

[burris]

Although all seems to be working well and I am still on Central02, the VPanel devices still show only one instance. Call records are up to date.

Since it is working, it really doesn't matter except to make you aware of it.
Maybe because line 2 still has a B after the number?

[KenH]

Returned HT502 to normal configuration. vPanel and HT502 CPL show both ports registered. I notice that now, NAT is shown as Symmetric, rather than Full Cone.
Incoming & outgoing calls are OK.

[buckethead]

Update from me - I have not made any changes since the initial changes last night which did not involve making it unregistered and I am still up and working. No issues so I have not touched any settings today.

Forgot to add - vPanel has only shown one device registered the whole time. I do not have a 2nd phone hooked into FX2 so have not tested or anything there.

[quattrohead]

I did not partake in any of this testing, but I do have the 502 registered 3 times in the CP !!!
502 is currently outside the router but I would like to move it back in sometime.

[Xponder1]

Update 9:02 PM CST. Still setup with test configuration. Outbound calls using 7 digits on port 2 go to a busy signal again. Inbound calls work on both ports. Add the area code and the call goes threw. Have not tested a 800 number. Brandon had this fixed last night did something change?

I will reboot my ATA and try again in a little while.

[VOIPoTim]

Update 9:02 PM CST. Still setup with test configuration. Outbound calls using 7 digits on port 2 go to a busy signal again. Inbound calls work on both ports. Add the area code and the call goes threw. Have not tested a 800 number. Brandon had this fixed last night did something change?

I will reboot my ATA and try again in a little while.

Everyone should be able to revert to the normal configuration without issues now as well.

[Xponder1]

Everyone should be able to revert to the normal configuration without issues now as well.

Ok I will say that when I rebooted it had the same issue. I will go ahead and revert as requested.

[Xponder1]

I reverted back and logged in and took a look at the settings and it shows a outbound proxy (sip.voipwelcome.com) on port #2 and not on port #1 and port number 2 unregister on reboot is set to no. Port 1 is set to yes.

Phone is working fine on both ports.

[orum]

This did make me think of a feature request...

I don't need an SMS for every call/voicemail, but it would be great to have an option to send an SMS if Failover (either to voicemail or another number) is "triggered".

Dan

[bretski]

I dropped again today. Noticed it when outbound calls would not complete. Looked at vPanel, no devices registered. Power-cycled, and it came back up.