Vectoring - Silently forwarding callers using VDN variables
If you read Vectoring - “Intercepts” and forwarding callers to other numbers, you probably realized that following the steps in that post to silently forward callers to a different destination using VDN variables can be made much less complex than what that required. Indeed it is: there’s only one vector step needed: route-to.
display vector 503 Page x CALL VECTOR Number: 503 Name: SilentRouteToV3 Multimedia? n Attendant Vectoring? n Meet-me Conf? n Lock? n Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y Prompting? y LAI? y G3V4 Adv Route? y CINFO? y BSR? y Holidays? y Variables? y 3.0 Enhanced? y 01 02 route-to number V3 with cov y if unconditionally 03 stop
The only reason that I used V3 for the destination number was because it matches the configuration that I used for the intercept vectoring mentioned previously; it really doesn’t matter which VDN variable you pick, so long as you’re consistent system-wide.
Here’s an example VDN:
isplay vdn 7406535223 Page 1 of 3 VECTOR DIRECTORY NUMBER Extension: 740-653-5223 Name*: ict-7406535223 Destination: Vector Number 503 Attendant Vectoring? n Meet-me Conferencing? n Allow VDN Override? n COR: 6 TN*: 1 Measured: none VDN of Origin Annc. Extension*: 1st Skill*: 2nd Skill*: 3rd Skill*: * Follows VDN Override Rules
Pay particular attention to the “Allow VDN Override?” setting – it’s “n”, which prohibits variables from being overridden by other VDNs. All VDNs which point to a vector that blindly routes to a destination should be set to “n” so that potential vulnerabilities in other VDNs or vectors cannot be exploited and potentially escalated into an off-net forward.
display vdn 7406535223 Page 2 of 3 VECTOR DIRECTORY NUMBER AUDIX Name: Return Destination*: VDN Timed ACW Interval*: After Xfer or Held Call Drops*? n BSR Application*: BSR Available Agent Strategy*: 1st-found Used for BSR Polling? n BSR Tie Strategy*: system Observe on Agent Answer? n Send VDN as Called Ringing Name Over QSIG? n Display VDN for Route-To DAC*? n VDN Override for ASAI Messages*: no BSR Local Treatment*? n Reporting for PC or POM Calls? n Pass Prefixed CPN to VDN/Vector*? system * Follows VDN Override Rules
display vdn 7406535223 Page 3 of 3 VECTOR DIRECTORY NUMBER VDN VARIABLES* Var Description Assignment V1 V2 V3 route_to 7900 V4 number_old 7406535223 V5 number_new 7406527900 V6 handle_method 3 V7 V8 V9 VDN Time-Zone Offset*: + 00:00 Daylight Saving Rule*: system Use VDN Time Zone For Holiday Vectoring*? n Apply Ringback for Auto Answer calls*? y * Follows VDN Override Rules
You can see that the V4-V6 are also assigned, which is because this VDN previously pointed to vector 502 (the aforementioned intercept vector). Those variables are no longer used, and are simply ignored since the vector doesn’t use them.