An oddity for sure. The switch had been running for a long time, then I moved to a new location and ended up with a new subnet.
I lost the login password so I added a new domain (pbx) with a new admin, and updated users.
I had my phone (Yelling T48G) with two DIDs and I was able to call between them but inbound and outbound did not work.
The ext IP (static) was updated and working as I could see calls talking with the carrier via sngrep.
Then suddenly the phone would not register, just met with no reply. After a bunch of debugging I gave up two days later.
But on day three the extensions were registered and calls could be made between them.
I had inbound working but would go to VM even though it was supposed to ring the phone as it had always done.
Going through the log I noticed that the valet_context said pbx, the temp domain to gain access once again.
I figured out how to allow the admin to remove the 2nd domain and did so, but housekeeping seems to be falling behind again as the log still shows pbx.
I've rebooted stopped/started SIP, rescanned and reloaded a few times.
I've tried to see how to manually run something that activates the db housekeeping but not sure what to run and hesitant to execute scripts randomly.
At this point I'm going to wait and see if it once again cleans up, and of course if someone here comes back with something that can help me go forward.
Grateful for any tips!
I lost the login password so I added a new domain (pbx) with a new admin, and updated users.
I had my phone (Yelling T48G) with two DIDs and I was able to call between them but inbound and outbound did not work.
The ext IP (static) was updated and working as I could see calls talking with the carrier via sngrep.
Then suddenly the phone would not register, just met with no reply. After a bunch of debugging I gave up two days later.
But on day three the extensions were registered and calls could be made between them.
I had inbound working but would go to VM even though it was supposed to ring the phone as it had always done.
Going through the log I noticed that the valet_context said pbx, the temp domain to gain access once again.
I figured out how to allow the admin to remove the 2nd domain and did so, but housekeeping seems to be falling behind again as the log still shows pbx.
I've rebooted stopped/started SIP, rescanned and reloaded a few times.
I've tried to see how to manually run something that activates the db housekeeping but not sure what to run and hesitant to execute scripts randomly.
At this point I'm going to wait and see if it once again cleans up, and of course if someone here comes back with something that can help me go forward.
Grateful for any tips!
