Hi there, I have OBI 202 at firmware 3.2.2 (Build: 5921EX). I have Callcentric on SP2 (GV on SP1 and is the PL) and I can check my voicemails on it by dialing "*86" via SP2. I went through some old threads and I understand that I can simply re-code the definition (or action) of "*86" in Star Code Profile A (My only Ph uses profile A) without changing any DMs or OCR. I got that working by changing the action of "*86" line to:
"*86(<sp2(*86)>), Callcentric VM, call($Code)". Thanks, @azrobert.
I also got it working by changing the DMs and OCR (I re-coded "*86" in the Star Code Profile A to call my cell phone for testing). I added these:
ITSB Profile A DM: |<**2>*86|
ITSB Profile B DM: |*86|
PH OCR: {*86:sp2}
The above rules work and the "*86" star code action (to call my cell) is never invoked and I can connect to my CC VM.
I wanted to take it further by NOT re-purposing "*86", but using my custom sequence to get to the CC's VM. I picked "#22". I had a choice of 2 options.
OPTION 1: Validate & Replace "#22" in ITSB DMs and pass the correct dialing number to PH OCR. I added these:
ITSB Profile A DM: |<#22:**2*86>|
ITSB Profile B DM: |<#22:*86>|
PH OCR: {*86:sp2}
OPTION 2: Just validate "#22" in ITSB DMs and change it to the correct dialing number to PH OCR. I added these:
ITSB Profile A DM: |<**2>#22>|
ITSB Profile B DM: |<#22>|
PH OCR: {(<#22:*86>):sp2} and {(<**2#22:*86>):sp2}
None of options 1 or 2 work. In Option 1, I noticed that it is blowing up while doing DM validation and I don't see any entries in the Call log. When using Option 2, the call is logged, but OBI is sending "#22" to SP2 and not "*86", meaning the PH OCR does not replace the "#22" (or its "**2#22" variant) to "*86" before the handover to SP2. Any ideas? Thanks.
EDIT: I add these rules to the start of the respective DMs and OCR. Also, I have tested with "##22", "###22" and "#86". Same no go. (When using "#86", I simply replace "#" to "*" in both options 1 and 2. Something like "<#:*>86", and not worrying about "22")