SIP connected switched playing announcements

[learn2shoot]

We have multiple switches which are SIP connected - to hit the other switch we dial 79-402 (then the 7 digit extension) so from my desk extension I can dial 79-402-399-1541 and head it on my 9640. However if I create a Vector the announcement the field for the extension doesn't allow that many characters (only 8 characters are allowed)

I think the question is - How can I change the length of what is accepted in the Announcement Field?
I am open to other possibilities of a fix - the next question will be an internal decision - do we want to do this?

My trace looks like this when I put the whole 794023991541 in the VDN variable V1....

10:39:05 TRACE STARTED 09/15/2015 CM Release String cold-03.0.124.0-22101
10:39:14 0 0 ENTERING TRACE cid 8268
10:39:14 4242 1 vdn e1930002 bsr appl 0 strategy 1st-found override y
10:39:14 4242 1 announcement V1
10:39:14 4242 1 variable V1 = [79402399] vdn var
10:39:14 4242 100 stop
10:39:14 4242 100 LEAVING VECTOR PROCESSING cid 8268
10:39:14 4242 100 TRACE COMPLETE cid 8268

My Vector looks like this:
CALL VECTOR

Number: 4242 Name: Bill.TEST.91515
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 route-to number V1 with cov n if unconditionally
02
03


My VDN looks like this
VECTOR DIRECTORY NUMBER

Extension: 193-0002
Name*: Bill TEST 9.15.15
Destination: Vector Number 4242
Attendant Vectoring? n
Meet-me Conferencing? n
Allow VDN Override? y
COR: 51
TN*: 1
Measured: external

Service Objective (sec): 20
VDN of Origin Annc. Extension*:
1st Skill*:
2nd Skill*:
3rd Skill*:
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

VECTOR DIRECTORY NUMBER

VDN VARIABLES*

Var Description Assignment
V1 Announce LDC 794023991541
V2
V3
V4
V5
V6
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

 

[ZeroZeroOne]

So this is your setup? Vector and VDN are on System 1. Announcement is on System 2.

The Announcement command will only play an announcement local to the system, so you would need to either record or copy the announcement from System 2 to play it locally, or create a unique VDN / Vector on System 2 and route the call there and let that system control the call.

 

[kyle555]

I agree with the guy above. You can't reference announcements on the other system.

Maybe having a common dial plan range for announcements and moving the wav files to whatever announcement source you use would be helpful.

I guess I could see a complication if you have the same announcement on 2 CMs and have call center supervisors re-record one announcement on the fly - you wouldn't be able to just do it from the telephone one time.

 

[learn2shoot]

I was afraid that would be the answer. Thanks

ZeroZeroOne - yes that is the setup I was hoping for.

Kyle555 - Not worried about that; the supervisors do not record announcements and if they did that's a small concern, but worth thinking about.