Is the field "CallForwardOnNoAnswerNumber" an "Inbound Call Route"?
dani:
Yes, now I realize I was talking about something different:
On the current settings, my voip provider doesn't have my own nr as default outbound callerID number, and expects it to be provided on each call.
Can I have the Obi provide explicit callerID number on every voip outbound call?
It would be nice to do it both when the digitmap sends something to SP2, and when using **2.
Thanks, and sorry for the confusion.
RonR:
Quote from: dani on April 16, 2012, 11:42:15 pm
On the current settings, my voip provider doesn't have my own nr as default outbound callerID number, and expects it to be provided on each call.
Can I have the Obi provide explicit callerID number on every voip outbound call?
It may be possible to use the Voice Services -> SPx Service -> URI parameter to accomplish what you want. It's not clear to me how CallerID spoofing interacts with this, so more experimentation will be required tomorrow.
From the OBi Device Administration Guide:
This parameter affects the way the AOR is formed by the device in outbound SIP Requests. The AOR has the format: user@domain.
If the value of URI is empty, device gets the user portion of its AOR from the AuthUserName, and the domain portion the value of ITSP Profile’s UserAgentDomain if it is not empty, or that of the ProxyServer otherwise.
If the value URI is not empty and does not contain “@”, it is used as the user portion of the AOR while the domain portion is formed the usual way.
If the value of URI contains “@’, it is interpreted as a full AOR and device takes it as the AOR as is.
Some Examples:
1) Let ProxyServer = sip.myitsp.com, AuthUserName = 4089991123, URI=[empty], UserAgentDomain=[empty], then
AOR = 4089991123@sip.myitsp.com
2) Change UserAgentDomain to users.myitsp.com, then
AOR = 4089991123@users.myitsp.com
3) Change URI to bobdylan, then
AOR = bobdylan@users.myitsp.com
4) Change URI to bobdylan@superusers.myitsp.com, then
AOR = bobdylan@superusers.myitsp.com
dani:
Interesting.
My test before calling it a night:
I put my nr in the URI field, as 2223334444.
Called to GV, caller id shows as +12223334444.
Called my cellphone, and the call was REJECTED by the service provider.
Let's see tomorrow....
Thanks
RonR:
Quote from: dani on April 17, 2012, 12:53:37 am
I put my nr in the URI field, as 2223334444.
Called to GV, caller id shows as +12223334444.
Called my cellphone, and the call was REJECTED by the service provider.
After some additional testing, ...
Since your service provider expects you to provide your own CallerID, putting your PSTN number in the URI parameter appears to accomplish exactly what you want (I would use 12223334444). When incoming calls are forwarded to another number with X_SpoofCallerID enabled, your CallerID (in the URI parameter) gets overridden by the caller's as one would hope.
I don't understand why you were able to successfully call one number (Google Voice) but have a call to another number (cell phone) rejected. Is this reproducible, and if so, can you tell what's going on from looking at the two calls with WireShark?
infin8loop:
I put my PSTN phone number in Voice Services -> SP2 Service -> URI as 11231231234
on the same Obi that has Line CallForwardOnNoAnswerNumber : sp2(10555) to the voip.ms mailbox.
This fixed the callerid number for outbound calls on voip.ms. I didn't know there was an issue because I haven't made any outbound calls on voip.ms since getting rid of the DID I had for testing. I had the DID in the callerid override in the voip.ms primary account and had no subaccounts at the time. Now I use two subaccounts and leave the primary account unregistered. I never populated the callerid number override in the voip.ms subaccounts configuration.
With the URI populated on the Obi I made test calls through the voip.ms subaccount_1 on sp2 to my cell, GV, and my other PSTN line. All calls received showed the proper callerid number (the one in the URI) and the receiving PSTN line showed the correct callerid number and name (confirming AT&T looked it up correctly).
The Line CallForwardOnNoAnswerNumber : sp2(10555) still works in that the callerid number of the inbound calls are kept when sending calls to voice mail.
Thanks RonR. I would have never gleaned this information from manual. I remember reading the description of the URI and going, "huh?". LOL
"It's always something" - Roseanne Roseannadanna didn't know she could have been talking about voip.
Navigation
[0] Message Index
[#] Next page
[*] Previous page