Any way to get Message Waiting Notification from the PSTN line?
infin8loop:
I put a voice mailbox at voip.ms (on SP2) on my PSTN line by setting:
Physical Interfaces -> Line Port -> Calling Features ->
CallForwardOnNoAnswerEnabled : checked
CallForwardOnNoAnswerNumber : sp2(0118835100xxxxxxxx)
CallForwardOnNoAnswerRingCount : 5
Where "0118835100xxxxxxxx" is a free iNum DID provided by voip.ms. In the menu at voip.ms DID Numbers -> CallerID Filtering I have a rule for inbound from 0118835100xxxxxxxx to immediately go to the voice mailbox (also on failover conditions Busy, No Answer, and Unreachable). The originating callerid number is lost in the forward to voip.ms (which actually makes this Rube Goldberg work) so I have "say callerid" turned off in the voip.ms mailbox configuration. MWIEnable and X_VMWIEnable are checked on SP2. I turned the answering machine off on the base unit of the cordless system connected to the phone port. I have speed dial #2 set to **2*97 to retrieve voice mail from voip.ms. There is no charge from voip.ms for this forwarding because it's voip.ms DID to DID dialing (the iNum is effectively calling itself.. think about that for a second and it may still not make sense to you, a drink might help). I get the stutter VM waiting sound but I guess my cordless doesn't support the visual indicator. I probably couldn't see the indicator anyway. Since I configure my OBi locally (No, I'm not brainwashed nor a cult member although perhaps newbeeish at times and slowbeeish at others) I have speed dial #1 set to my google voice number because dialing 1# and 2# seems intuitive to me to retrieve VM from SP1 and SP2 respectively. The ObiTalk portal would force speed dial #1 to a soft phone that I don't ever use (unless I'm experimenting).
This method of madness probably (maybe?) could be adapted for use with voip providers other than voip.ms.
It's not exactly what you wanted or needed, but with the OBi, what is?!?
dani:
infin8loop: yes, most of it makes sense and seems a good way to restore the natural order of things (at least to the way the phone users here are used to).
The only thing I'm not sure about is why caller id gets lost. Is it because it's an iNum? what if you forward to a sub acct or other kind of virtual sip?
In any case caller id is stored in the Obi history (which I poll and save on an hourly basis)
This may be a good excuse to shave the mailbox from the Bell phone bill. It could even pay for an extra real DID, if that would help in any way.
Thanks for the suggestion.
hwittenb:
Quote from: dani on April 13, 2012, 11:39:32 pm
The only thing I'm not sure about is why caller id gets lost. Is it because it's an iNum? what if you forward to a sub acct or other kind of virtual sip?
Dani,
You can retain the caller id if you do the forwarding to voip.ms as a sip uri and you have set X_SpoofCallerID yes in the ITSP Profile for the SPx sip account, for example forward to SP2(5141231234@losangeles.voip.ms) or SP2(5141231234@sip.voip.ms).
Be aware that setting X_SpoofCallerID can cause other problems if you are using the automated attendent (AA) to bridge other calls and your voip provider does not allow a spoofed caller id.
Edit: The reason the caller id gets "lost" is because the call is forwarded by voip. Voip providers require authentication to terminate calls. As part of authentication many/most voip providers who authenticate by userid and password do not allow "spoofed" caller id's. They want to see the caller id that is represented by your account. A few who authenticate by ip address are not that rigid. You can setup a sub account under voip.ms that has an option to authenticate by a static ip address.
When you send a call by sip uri to a voip account it is like a normal incoming call that is not authenticated. I believe that is why you can "spoof" the caller id on the call.
dani:
Looks like I have some experiments to do. Thanks all for the suggestions.
infin8loop:
For the method I suggested, if the original callerid number is retained then it won't match the iNum filter at voip.ms that sends the call immediately to voice mail. I believe this would create another inbound call back to the OBi and the caller would have to wait longer for that bridged part of the call not to be answered and then be put to voice mail. I have not tested this but this looks like it could be adjusted by fiddling with the voip.ms DID setting "Dial Time Out in seconds" for the iNum which looks to be set at a ridiculous 60 seconds (12 rings. I don't recall setting this but maybe I did). In our case I don't want to set it too low because the iNum is also used for inbound calls by some of my daughter's International friends from summer camp and it needs to be high enough for calls to be answered if there is someone here to answer them. I appreciate the feedback and dialog this has created!
Navigation
[0] Message Index
[#] Next page
[*] Previous page