Any way to get Message Waiting Notification from the PSTN line?
hwittenb:
infin8loop,
Looking at the voip.ms offerings, if you wanted to retain the incoming caller id on the forwarded call to voip.ms, I believe you could get a "Virtual SIP Number" from voip.ms and setup routing for all calls to the virtual sip number "DID" to go directly to your voip.ms voicemail. On the OBi you would do your forwarding to the sip uri for your virtual sip number and also on the OBi setup X_SpoofCallerID for your SPx that you will use for the forwarding. I haven't tested this, but I believe it would work.
I think the forwarding to the "virtual sip number" would also be fairly fast.
infin8loop:
hwittenb,
The voip.ms "Virtual SIP Number" works great and the callerid is retained on calls sent to the mailbox when using the sip forward. The virtual sip number is just 25 cents a month (less than a penny a day). In this scenario it looks like there is no per minute charge levied. Otherwise It's only 1/10 cent per minute for virtual sip numbers. I noticed the "virtual sip numbers" before but never realized why I would use one. It's always helpful when someone "connects the dots".
Great info. Thanks.
dani,
Hopefully this gives you another option to experiment with. A voip.ms virtual DID URL in the form
sp2(11aaaaaaxxx@servercity.voip.ms) can be substituted for the iNum in my original post where "All virtual numbers consist of the following digits: 11 + Accountcode + 3 digits of your choice for a total of 11 digits.".
Using this method, no CallerID filter is needed at voip.ms. Just configure the virtual SIP DID to go to voice mail immediately.
dani:
Been working on this:
Got the virtual sip connected to the mailbox, got the Obi to forward on No Answer. That part works fine.
Also programmed the "VM" button on the phone to dial **2*97. Success so far.
Not so successful:
- Even when ITSP Profile B -> SIP -> X_SpoofCallerID has an X, I still get my own Caller ID. Not sure why...
- just realized that replacing Bell Answering Service with a voip.ms voicemail works fine on NO ANSWER, but not if the PSTN port is BUSY. The ForwardOnBusy only works when the PHONE is busy but the LINE is free.
Far-from-ideal workarounds I can think of:
1) use voip.ms mailbox on busy and bell mailbox on busy (very awkward to manage, plus still paying BELL)
2) do not use the PSTN for outgoing local calls (expensive if going out through voip.ms, caller-id messes up if going out through GV)
Thanks all for your help.
hwittenb:
Dani,
You don't have any way to know someone is calling your pstn line when it is busy, only the phone company knows that. Of course you can hire them to forward somewhere on busy but the last time I checked my phone company wanted $7.50/month for that little feature. Another choice is to add call waiting to your pstn line but that also costs money and gets a little complicated pressing the flash to the phone line to answer the call.
You can put your outgoing calls thru a different provider that costs less than voip.ms. Localphone goes for 0.5c per minute. You can set your caller id with them. I don't think their voice quality is quite as good as voip.ms. You can configure both voip.ms and localphone on your adapter using one of the voice gateways for localphone.
As for the caller id on a sip uri call, I don't know what the problem is there. I setup my OBi110 on the Line Port to forward on no answer to a sip uri and I monitored the outgoing voip call packets with WireShark packet trace. The outgoing Sip Invite showed the CallerID in the sip INVITE header field in both the From: and the Remote Party ID: fields. So in my case it is sending it.
Of course the OBi has to receive the incoming caller id from the pstn line. The OBi has a Call History function. When you look at the Call History you should see the incoming call on the Line and the outgoing call for the Call Forward. I initially thought that was a reliable way to tell if the original caller id went out with the forwarded call but it is not reliable. The "Peer Number" shows whether or not it went out with the forwarded call. The "Peer Number" is the incoming caller id. I ran some tests with X_SpoofCallerID on the ITSP Profile B for my SP2 both enabled and disabled and monitored the results with WireShark. That is the setting that does make the difference.
The OBi also has a syslog function that is almost worthless for debugging. It will show, however, if an incoming caller id is detected on an incoming pstn line call on the Line Port, but the Call History also does that.
To run a WireShark trace you need to run the packets thru an old hub, not a switch, with both your pc and you OBi attached so that your pc can see all the packets going to/from the internet. The hub is hard to find if you don't have one.
dani:
The plot thickens:
I've been testing this, and found the following:
- the phone NR is overwritten, but the original NAME (if available) is forwarded.
- voip.ms is charging me for the incoming forwarded call. It looks like the Obi transfers the analog call so voip.ms considers it Inbound DID instead of Inbound SIP
- I also tried to forward to sp2(11xxxxx9999@sip.voip.ms) instead of @toronto.voip.ms. The mailbox behaved differently (didn't play my custom msg) and the VMI didn't work.
Are any of these settings related? Do you guys have the defaults on them?:
X_UseRefer
X_ReferAOR
X_Use302ToCallForward
X_InsertRemotePartyID
X_MWISubscribe
X_MWISubscribeURI
Thanks
Dani
Navigation
[0] Message Index
[#] Next page
[*] Previous page