IPO release 7.0, caller ID pass through on forwarded calls

[Straggle]

Hello all,
I have a taxi company customer with IPO 500v2, release 7.0, who is implementing a 3rd party IVR dispatch partner company.

All we have to do on the IPO is call forward the DID calls to the IVR company's number, and allow the caller ID to pass through the IPO on the call.

I found this possible solution on another comment string, and I have build the following short code for the forwarding "user" to attempt to pass the caller ID.
9N
dial
NSS

I then use the User's "Forward" tab to forward unconditional to 91xxxxxxxxxx. (There are no user licenses that would allow twinnnig)

The carrier (XO, in San Francisco) told me to "pre-pend" the outbound caller ID string with *15 so I tried *15NSS and N*15SS and NS*15S and NSS*15 in my ARS table; no luck.

Seems I've got a few choices:
1) get a Power User license to allow the Mobile Twinning option, which would take advantage of the "Send original calling party information for Mobile Twinning" option. Or.
2) Upgrade the system to 9.0 or 9.1 and hope that the "NSS" part of the 9N short code will work. Or.
3) Do both.

Does anyone have any thoughts about this?

Thanks in advance!

 

[pmcook]

If you know the PU license enables what you need then why buy anything else unless you have a known reason to upgrade to 9.1? A PU license is typically 100.00 give or take. You've already blown more than that messing with it. No harm upgrading to 9.0 or higher since twinning comes with it. The cost is also fairly nominal. 9.0 and 9.1 have some nice hunt group improvements. At very least 100 bucks will do the job and any company that cannot afford that is not really in business. This actually is the job for a PRI.

 

[Straggle]

Ok, all done, and 100% successful, without needing the Power User license, or twinning feature.

The carrier is XO, and they (as a security procedure) require that one of their numbers ALWAYS be the outbound DID. Upon request, they'll build the code *15 into their router to allow the system to send some other caller ID for THAT CALL ONLY.

My main ARS table (51) has the code Nsxxxxxxxxxx for all normal outbound calls to meet the security restriction mentioned above; when I did this install years ago I did not know that the *15 code could be requested. Of course, a system-wide shortcode of 9N points to that ARS for all calls.

I then created ARS table #59 for this service that calls are being forwarded to, and cleared the outbound CLID which was sent by the code Nsxxxxxxxxxx code by replacing it with the code Nss

I then created an H323 user (no physical phone needed) and set up a user shortcode of 9N to point to my new ARS table (59). Once that was done I went to the user's Forwarding tab, and forwarded unconditional to 9*151xxxxxxxxxx (access code of 9, *15 code to bypass CLID security restrictions, 1 area code number).

This resulted in the original CLID to pass through my customer's system, and show up on the destination of the forward.

Again, the *15 code will work with XO, but I'm not sure about other carriers.

The *15 was necessary, as was the NSS in the ARS table.

Success!