Any way to get Message Waiting Notification from the PSTN line?
hwittenb:
More testing today. Reviewing my notes from January, at that time, with the settings discussed, I could forward calls to the landline attached to my OBi to voip.ms and they would pickup the original caller id from the forwarded call. Now they do not do that, they substitute. They changed something. I ran some additonal tests using another provider, CallCentric. You can forward sip uri calls to your CallCentric number by using their "Call Treatments". You forward to cc#@in.callcentric.com. If you forward a call to your CallCentric number to your voip.ms virtual number then voip.ms will pickup the original caller id from the call to your CallCentric number. In other words they accept the pass thru by CallCentric.
If you take that a step further and forward (by sip uri) the calls to your OBi attached landline to your CallCentric number which is forward to your voip.ms virtual number then the original caller id is passed thru the chain and accepted by voip.ms.
My conclusion is that voip.ms is looking for something unique to ata's in the Sip Invite sent by OBi's call forwarding that is not contained in Sip Invite sent by CallCentric to voip.ms.
infin8loop:
Have you tried using just the voip.ms "Internal Extension Number" associated to the subaccount? Something like sp2(10555) instead of the sip url sp2(aaaaaa555@toronto.voip.ms). Where 10555 is the "Internal Extension Number" associated to subaccount aaaaaa_555 and no device is registered to the subaccount? This of course assumes sp2 on the Obi is registered to voip.ms.
This keeps the inbound callerid id intact for me. But then again, using the virtual sip number in a sip url also works for me as well.
dani, check your "My Messages". I can't guarantee I can get to the bottom of why this doesn't work for you and it works for me. Maybe I'm talking oranges and you all are reading apples. I figure if I start getting spam calls I can just kill the IPKall number. LOL
I need a new hobby. Curling. Yeah, that's it. Curling. That ought to work out just great in Texas. Just shoot me now.
hwittenb:
With some more testing I finally got my OBi110 working with an inbound pstn line call simultaneously ringing the voip.ms sip virtual number using the Line Port inbound call routing {SP2(11xxxxxx001@sip.voip.ms),ph} and voip.ms properly picks up the original caller id. When I shifted to using the call forward entries none of them work at all with a number in sip uri format.
Changes I made from the original testing:
1. I could not have SP2 registered to voip.ms. It had to be to someone else.
2. I removed all my caller id override settings on voip.ms (main account, sub_accounts).
3. I repowered the OBi110 (remove power cord, reinsert it).
After I did the above, the caller id function started working correctly with voip.ms. I don't know if they all are really required.
dani:
hwittenb:
We did some tests with infin8loop, and realized the caller id override on voip.ms was the culprit. Consistent with your tests too.
Removing it fixes this, but messes up outgoing calls. Now the Obi must pass our own nr to voip.ms. Looking at how to do that.
Haven't gone the fake noanswerforward/delayed forking route yet. First want to see if this method pans out.
Thanks for your help.
hwittenb:
Quote from: dani on April 16, 2012, 11:15:56 pm
Removing it fixes this, but messes up outgoing calls. Now the Obi must pass our own nr to voip.ms. Looking at how to do that.
Dani,
I ran some test awhile back and for outgoing calls, most voip providers that authenticate outgoing calls by userid/password do not like spoofed ids for the caller id and as part of the authentication process reject the call. The Betamax companies allowed it, but ignored it and still used what they wanted.
You find a few cases where providers authenticate on your external ip address and might allow spoofed caller ids. Voip.ms has an option on their sub-accounts (sub accounts only) to authenticate by ip address. Of course, if you set this up you either need a static ip address or one that almost never changes. If you have the latter and your ip address changes you need to be aware why your outgoing calls suddenly stopped working.
Navigation
[0] Message Index
[#] Next page
[*] Previous page