Incoming Obi calls to use VOIP provider's voicemail (call forking to voip.ms)
Stewart:
Quote from: dailyglen on December 04, 2011, 08:04:45 pm
Using a speed dial as a SIP URI sounds interesting if it is free. Can you point me to more info or explain it further?
Unfortunately, I've lost control of my OBi, so can't test this now. However, I believe it should work to set up a Voice Gateway with AccessNumber of e.g. SP1(sip.voip.ms) and then set the speed dial value to e.g. VG1(yourDID).
If the above doesn't work, you could try iNum. If you don't already have one, get a free iNum DID on your VoIP.ms account, and send the call either via the remote OBi's provider (if they offer free calling to iNum), or via a gateway to sip.inum.net .
(I assume that this is only of academic interest, as it appears that infin8loop already solved your problem.)
RonR:
If you have any SIP Provider configured on SP1 and/or SP2, you can make SIP URI calls from Speed Dials:
User Settings -> Speed Dials -> 10 : SPx(883510000000091@sip.inum.net)
where SPx is SP1 or SP2 (must be configured for SIP).
dailyglen:
Hi RonR,
Thanks for the tip. Can I put SPx(883510000000091@sip.inum.net) directly in the CallForwardOnNoAnswerNumber field? Ideally, I want to use:
SPx($1 > 883510000000091@sip.inum.net)
What I am trying to do is make an extension in voip.ms which is basically a SIP URI so that I can forward unanswered calls to it which is routed directly to my voicemail. My problem with my current setup (above) is I have the wrong caller ID for the person who leaves the voicemail. So I want to spoof the caller ID to be that of the original caller. If I spoof the callerid and forward to my DID then I can't filter it to go directly to voicemail. Perhaps I need to use an inum for this but then this inum is useless except for leaving voicemail.
Thanks.
RonR:
dailyglen,
Much of this stuff is undocumented and you just have to try it to see if it works.
I suspect SPx(883510000000091@sip.inum.net) is valid in a CallForwardOnWhatever field, but I doubt that $1 is. $1 is only documented in conjunction with rule processing. Also, $1 didn't work correctly in earlier firmware versions, but it's not clear if it was a bug or a result of the intentional limiting of CallerID passing between trunks other than the OBiTALK trunk.
infin8loop:
Does anyone have any ideas what would cause the following speed dials (10 and 12) to fail:
SP2=voip.ms (SIP) xxxxxxxx=my iNum
10: SP2(8835100xxxxxxxx@sip.inum.net) fails with End Call (500 Service Unavailable)
11: SP2(0118835100xxxxxxxx) immediately answered by Voice Mail at voip.ms per a filter rule at voip.ms on inbound callerid number 8835100xxxxxxxx (calling myself) as expected
12: SP2(883510000000091@sip.inum.net) call connects but just dead air
13: SP2(011883510000000091) goes to iNum echo test and echo test works as expected
The number or url inside the parenthesis show up in the OBi log on the right side beside Peer Number under SP2/Outbound entries in the call log so I think they're being dialed correctly (a DigitMap isn't wonking it)
It's the SIP URIs that are not working. I'm pretty sure these worked a month or so ago. I don't think I've changed any parameters on the unit that would affect the SIP URI connectivity. Same router, no firewall changes. No Stun server on SP2 - never had one on it. Grasping at straws I forwarded ports 5060-5061 to the OBi - still no joy.
What bit have I twiddled incorrectly?
Navigation
[0] Message Index
[#] Next page
[*] Previous page