Hello all,
Yes rbermel83, I forgot I posted this question years ago , but today I received an email notification triggred by your post. I had to learn how to do it through trial and error, I suppose I posted this in the wrong forum? because I never did get the answer you can see.
I have good news for you though. The answer turned out to be mostly simple.
In ICM, use a "dyamic label" and after the dialed number add the suffix ";CLI=", and then add the calling line ID override after that.
So, for example, If I wanted ICM to transfer a call over the PSTN to 888-555-1212, and present an ANI of 300-123-4567, that dynamic label would contain:
"outbound-prefix18885551212;CLI=3001234567"
Depending on the infrastructure, you may also need to add a prefix to route the call to an outbound or egress gateway.
Furthermore, the local switch that sends the call out over the PSTN may need the SBN/BNS option enabled for the LTDATA tuple on each of the outbound trunk groups used for these calls to permit a CallingLineID (CLID) override. Otherwise, it could stomp on the override with a billing phone number. Also, this SBN/BNS setting could have implications for 911 emergency calls. Be careful about this in a call center environment. Fortunately, you can set up rules on that same switch to dedicate a tunkgroup that does not enable the SBN/BNS option and configure that for any 911 calls.
At the destination, there could be one other hurdle, but for B2B it should be easy to overcome. The WAN PSID setting (AT&T example) may have to be enabled in the destination carrier ingress trunk groups to allow the field you are overriding here in the data channel (ISDN PRI-speak) to be preseted as the caller's ANI.
Best Regards!
