Voicemail to SP4
azrobert:
I had a test with the following speed dial and *98 in my Phone Port DigitMap:
*98, Set Speed Dial, set($Spd[99],99)
When I dialed *98, it was sent out SP2 and Speed Dial#99 was unchanged.
I removed *98 from the Phone Port DigitMap and reran the test.
Nothing went out SP2 and Speed Dial#99 was set to 99.
I verified this by just looking at Speed Dial#99.
The only explanation for the above behavior is that Phone Port DigitMap gets control FIRST and then the Star Code DigitMap.
Retry your Case 2 with the following mod:
Case 2 - *98, Voice Mail, call(**1*44)
I bet *98 will be sent out SP1 and not *44
azrobert:
Quote from: azrobert on October 06, 2013, 02:56:02 pm
Retry your Case 2 with the following mod:
Case 2 - *98, Voice Mail, call(**1*44)
I bet *98 will be sent out SP1 and not *44
Just want to clarify what I think will happen with above suggestion.
If *98 is NOT in your PP DigitMap **1*44 will be sent to the PP outbound route.
If *98 is in your PP DigitMap *98 will be sent to the PP outbound route.
I don't think your Case3 will get a match after dialing *98.
The Star Code DigitMap checks for extra digits dialed after *98.
You would have to dial *98*98 to get a match.
ianobi:
Quote
Retry your Case 2 with the following mod:
Case 2 - *98, Voice Mail, call(**1*44)
I bet *98 will be sent out SP1 and not *44
I was all ready to collect the $1000 bet money :D then things got confusing ???
Case 2 - *98, Voice Mail, call(**1*44)
In my case *44 is sent out of sp1 as I would expect. This works every time so long as token in call(token) can be matched in my Phone Port OutboundCallRoute.
My problem now is that I cannot make Case 3 work at all even the way I had it yesterday!
I still believe that Star Codes are processed before digits get to the Phone Port DigitMap. However, there may be some subtle differences in the way OBi deals with different Star Codes. Here's a quote from the AdminGuide:
Quote
Star Code Script Actions (ACT)
The general format of an action: ACT(par, par, ….)
The following actions are supported:
set(VAR,token) = Set the given VAR to the value represented by token.
call(token) = Call the number represented by token.
o PHONE Port::OutboundCallRoute will be applied when making the call (but not the DigitMap)
rpdi(token) = repeat dial the number represented by token
coll(VAR) = collect a number from the user and store it as the value of the parameter(s) represented by VAR.
o The number is collected with PHONE Port::DigitMap applied
say(token) = announce the value represented by token
o Values are announced as a list of alphabets or numbers
where token can be a literal (such as 1234) or another variable (such as $CFAN or SP1($CFBN))
It seems that "call" is dealt with in one way and "coll" the number is dealt with differently. There's a lot more here to think about!
I will come back to the whole subject of precedence - phone port / star codes / speed dials / trunk dialling - what digits get processed first etc? I'm busy with non-OBi stuff for a few days, so that will have to wait.
One of us should start a new thread "Star Codes - Some Observations". We seem to have hijacked this one for our own purposes! I wonder if threehappypenguins found the answer she was looking for!
Navigation
[0] Message Index
[*] Previous page