3.0.1 (4303) Can No Longer Receive Calls
chicobiker:
Ok, I have the latest firmware update installed in my obi200 and just made a remote change to sp1 then changed it back to what I had before so my obi would recycle. I am very remote from my obi right now and was hoping this would work vs power recycle. Just called our obi and can report that it now rings correctly and goes to voice mail normally. Hoping everyone's is fixed.
gderf:
It's fixed now.
What I am not sure about is that X_EnforceRequestUserID appears to be disabled by default, and X_InboundCallRoute is set to 'ph' only. Is this the intended configuration?
obi-support2:
X_EnforceRequestUserID is disabled by default (in 3.0.1.4318) but you can change it by yourself using the Expert Config on OBITALK if you need it.
Regarding ph or ph1,ph2, I believe this is the option you picked when used the setup wizard originally.
gderf:
Quote from: obi-support2 on March 03, 2014, 02:41:50 pm
Regarding ph or ph1,ph2, I believe this is the option you picked when used the setup wizard originally.
When I set my OBi up originally it was set to {>[Your Account User ID]:ph} all by itself. I never specified that.
Mango:
Quote from: obi-support2 on March 03, 2014, 02:22:32 pm
This rule {>[Your Account User ID]:ph} will no longer work
It seems like a pretty bad idea to have different versions of syntax that work with different firmware versions, especially since there was no inherent problem with the syntax before.
Navigation
[0] Message Index
[#] Next page
[*] Previous page