*98 doesn't work
hanshen:
After a few testing, I am sure the issue with OBi settings.
RonR,
Can you please verify this I am finding that might be conflict issue.
Voice Services -> SPx Service -> MessageWaiting : (unchecked) (Default unchecked)
I've checked the manual that MessageWaiting is actul state instead of configure parameter. Is that meaning:
MessageWaiting state is 'checked': there are messages waiting;
MessageWaiting state is 'unchecked': there are not messages waiting;
and previous digitMap save issue, the following Auto Provisioning has to be disabled:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
Can you please confirm if they are conflict?
And futher, there is parameter, MWISubscriber_Expire default set 3600 (sec) i.e. 1 hour. Is that caused the MWI delay an hour "on" or "off"?
RonR:
Quote from: hanshen on March 29, 2012, 07:45:48 am
Voice Services -> SPx Service -> MessageWaiting : (unchecked) (Default unchecked)
I've checked the manual that MessageWaiting is actul state instead of configure parameter. Is that meaning:
MessageWaiting state is 'checked': there are messages waiting;
MessageWaiting state is 'unchecked': there are not messages waiting;
Yes (at least that's what the OBi thinks).
Quote from: hanshen on March 29, 2012, 07:45:48 am
and previous digitMap save issue, the following Auto Provisioning has to be disabled:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
Can you please confirm if they are conflict?
In order to configure the OBi directly, you MUST set:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
In order to configure the OBi through the OBiTALK Web Portal, you MUST NOT disable them.
You MUST use one method of configuration or the other, NOT both.
Quote from: hanshen on March 29, 2012, 07:45:48 am
And futher, there is parameter, MWISubscriber_Expire default set 3600 (sec) i.e. 1 hour. Is that caused the MWI delay an hour "on" or "off"?
I believe an MWI Subscription is like a SIP Registration. It's in effect for a period of time and must be renewed at or before it expires in order to keep the Subscription in effect. While the Subscription is in effect, the SIP server will send NOTIFY messages to the SIP client informing it of any changes in status.
hanshen:
Hi, RonR,
What I want to know are
1. If MessageWaiting state (checked or unchecked) was not changed while new message coming or message cleaned, is due to
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
2. There are actually MWI on when new message coming or MWI off when message cleaned, took long time (about an hour), If it's related to
MWISubscriber_Expire default set 3600 (sec) i.e. 1 hour.
RonR:
Quote from: hanshen on March 29, 2012, 11:01:01 am
1. If MessageWaiting state (checked or unchecked) was not changed while new message coming or message cleaned, is due to
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Setting:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
has only one effect on an OBi : It prevents the OBiTALK Web Portal from updating configuration settings in that OBi. It does not affect the operation of the OBi in any way.
Quote from: hanshen on March 29, 2012, 11:01:01 am
2. There are actually MWI on when new message coming or MWI off when message cleaned, took long time (about an hour), If it's related to
MWISubscriber_Expire default set 3600 (sec) i.e. 1 hour.
The X_MWISubscribeExpires setting should not affect the time it takes for MWI changes to occur. If the OBi is currently subscribed to MWI notifications, the SIP server should send NOTIFY messages whenever MWI status changes. You would need to ask the service provider if those NOTIFY messages are sent instantly or incur some delay.
hanshen:
So now, My testing results are:
1. When new message waiting, Voice Services -> SPx Service -> MessageWaiting :state is checked, however MWI on phone set took long time (an hour) to start flash;
2. After clean message waiting, Voice Services -> SPx Service -> MessageWaiting : state is unchecked, however MWI on phone set took long time (an hour) to be off;
MWI is actually working, what was wrong it took so long to reach MWI on phone??
Navigation
[0] Message Index
[*] Previous page