Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Manipulating the CPN on a per outbound call

Status
Not open for further replies.

john3voltas

Technical User
Nov 12, 2013
138
PT
Hello,
One of our customers needs to start showing a different CPN for outbound calls depending on the motive of the call.
If the call is to sell a product they want to show CPN 1, if the call is about invoices they want to show CPN 2, if the call is about tech support they need to show CPN 3 and so forth.

We know we can manipulate the CPN using the public unknown numbering table but that only allows 1 CPN per each station/loginID whereas in this case we would need around...60 different CPNs per each station...

To try to work around this issue we thought about creating 60 different VDN's with 60 different entries for those VDN's in the public unknown treatment form. We created a Vector that collects 9 digits and which then routes out those 9 digits using a route-to command.
This sort of works. The caller is asked for the number to be dialed. The Vector actually routes the call out but it doesn't respect the public unknown treatment entry for that VDN.
Actually, looking at a list trace station, it should advert that the CPN is being manipulated by the public unknown treatment entry but it doesn't. It simply dials the call out and simply ignores the PUT table.

Is there anything we are missing here?
Is there some (different?) way of achieving our goal?

Thanks in advance.

Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top