Is the field "CallForwardOnNoAnswerNumber" an "Inbound Call Route"?

(1/3) > >>

dani:
In other words... can the field "CallForwardOnNoAnswerNumber" take all the complex syntax options described in page 121 of the Admin Guide?

I ask because I'm looking for the right way to include the internal variable $1 in the bridging instructions, but i can't make it work...

Thanks

RonR:
No.  It can only be a telephone number in TK format : SP2(18005551212)

If you don't mind the PHONE Port continuing to ring until the call is answered by the forwarding number, you can do a simulated CallForwardOnNoAnswer:

InboundCallRoute : {ph,sp2(17771234567@in.callcentric.com;d=10)}

This will ring the PHONE Port for 10 seconds before a call is placed to 17771234567 at Callcentric.  The PHONE Port will continue to ring until Callcentric answers (or the caller gives up).

RonR:
dani,

I just ran several tests with WireShark to satisfy my own curiosity.  The results are the same as I and others have found in the past:


- X_SpoofCallerID must be enabled for CallerID to be passed

- {sp2($1>17771234567@in.callcentric.com)}   CallerID of "$1" is passed

- {sp2($2>17771234567@in.callcentric.com)}   CallerID of "$2" is passed

- {sp2(18005551212>17771234567@in.callcentric.com)}   CallerID of 18005551212 is passed

- {sp2(17771234567@in.callcentric.com)}   CallerID of caller is passed

$1 and $2 are passed as literal strings and not replaced by internal values as described in the OBi Device Administration Guide.  I've found the same thing is true when trying to use the $2 variable in OutboundCallRoutes.  I've asked Obihai about this in the past, but my emails went unanswered.

dani:
Hi RonR

This is very interesting and useful, because of the following:

A bit ago we were talking with infin8loop about this, and realized that voip.ms has a callerID setting for each subaccount/extension. If we leave this field BLANK, then caller number gets transmitted. If we put a value there, it overwrites the caller number. One would assume that this setting is for outgoing calls only, but its behavior became very clear in our experiments.

Now... leaving this field blank fixes the transfer of caller number when bridging a pstn call to a voicemail, BUT it wrecks outgoing calls, as they now have my voip acct# as caller number.

This is where your last message comes in: where exactly in my Obi settings should I put that string  ("mypstnnr > mysipnr@voip.ms"), so the Obi hardwires my callerid number when using SP2?

Thanks

Dani

RonR:
Quote from: dani on April 16, 2012, 11:10:21 pm

This is where your last message comes in: where exactly in my Obi settings should I put that string  ("mypstnnr > mysipnr@voip.ms"), so the Obi hardwires my callerid number when using SP2?


I'm not sure what you're asking.

What I was testing was call forwarding via SIP URI from an InboundCallRoute rule : {sp2(cid>callee)}

If you're wanting to hardwire the CallerID to your PSTN number as you forward a call to your voip.ms number, you would use:

{sp2(pstn_nmbr>voip.ms_nmbr@voip.ms)}

Navigation

[0] Message Index

[#] Next page