Any way to get Message Waiting Notification from the PSTN line?

<< < (5/7) > >>

infin8loop:
Quote from: dani on April 15, 2012, 09:01:12 pm

infin8loop

I got the bit about the charge. It's part of the virtual sip.

But... is this (working) setup you describe any different from what we've been testing until now?

I have:
sp2(111xxxxx999@toronto.voip.ms) on LINE CallForwardOnNoAnswerNumber,
LINE CallForwardOnNoAnswerEnable clicked
ITSP Profile B X_SpoofCallerID clicked

It all works, except the forwarding of the CID.

THanks


Yes, those are the parameters I have set. Except I use the dallas server, not toronto. I have U.S. AT&T PSTN service.  I have the Line Port RingDelay : 2500 (the default is 4000 but 2500 allows the phone to ring faster and still allows the callerid to be obtained.  In my case 2000 was too short).  If you're getting callerid in the Obi call history on the inbound call, I would think you'd be good to go with whatever you have it set at. Shouldn't matter but I have LINE Port CallForwardOnNoAnswerRingCount : 5.

Another option that came to me.  I set up another voip.ms subaccount (I already had 2, one for each Obi).  Let's say it's Username aaaaaa_555 and the Internal Extension is 10555 where aaaaaa is the primary account number.  Set Internal Extension VoiceMail to the appropriate mailbox. Set the Internal Extension Ringing Time to 1 second (don't think it matters, but it may).  Don't register a device to this subaccount.  
Then use sp2(10555) on LINE CallForwardOnNoAnswerNumber. It goes directly to voicemail because there's nothing registered to it (and maybe the ring delay of 1 second). This seems to work for me just as well as the virtual sip number. The subaccount is free and there is no per minute charge (not that either would break my bank).  Maybe, for whatever reason, you will get callerid in the mailbox using this method since it's an "internal call" and not a sip url.

hwittenb:
Dani,

I also did some additional testing sending the forwarded call to the voip.ms sip uri number.  The caller id is definetly going out with the settings described however voip.ms is changing it in their CDR records to my voip.ms account setting.  I can't figure out why.  It's failing some voip.ms test.  I'll work trying to find out the reason.

dani:
RonR: thanks for checking. It seems my settings are correct.

infin8loop: good idea to try with a subaccount. Will test it during daytime. I always imagined subaccounts needed a registered device to operate.

hwittenb: interesting to know it's not a goof in my setup, but rather something on voip.ms side. Maybe the "reverse" the spoofing?

Thanks all again...

UPDATE:
I tried with a subaccount. It forwarded fine, the billing was 0 as expected, but voip.ms didn't let itself get spoofed.
I checked in 3 places: CDR, email, mailbox readback, and all had the Obi nr. Bummer

dani:
I had the following exchange with voip.ms support:

ME:
I programmed my ATA to forward No-answer or Busy PSTN incoming calls to a voip.ms extension connected to a mailbox.
I also programmed the ATA to "spoof" the called id with the info from the incoming call, so the voicemail has the proper caller data.
The forwarding and voicemail works fine, but voip.ms CDR and voicemail shows those forwarded calls and voicemails as being originated by me, instead of the ID of the forwarded call.
Is there a way to modify my settings at voip.ms so the original caller data is recorded?

VOIP.MS:
You will be able to select the Caller ID override, please note that the call forwarding is an outgoing call from our system, so the caller ID displayed will be the one you set on the Caller ID override.
Please check our article here: http://wiki.voip.ms/article/Call_Forwarding

So... nothing new.

Just to try something different, i changed CallForwardOnNoAnswerNumber to tg4(109) and Trunk Group4>TrunkList to sp2. Hoping to be able to have wider syntax options (maybe $1) in the digitmap, but so far haven't found the right setup.

RonR:
Quote from: dani on April 16, 2012, 11:09:51 am

Just to try something different, i changed CallForwardOnNoAnswerNumber to tg4(109) and Trunk Group4>TrunkList to sp2.


It's unlikely that using a Trunk Group will help matters.  Trunk Groups are simply a way of specifying multiple trunks to use in case one of them is busy.

Navigation

[0] Message Index

[#] Next page

[*] Previous page