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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VSU - wont play welcome message?

Status
Not open for further replies.

lcns

Technical User
Jan 29, 2007
26
0
0
US
We are setting up a VSU to play a welcome and queue message on an incoming trunk call via an E1 to a Common Operator.

We have set up the CORGS, CALT and RA commands but it will not play.

Internal calls to the OC work fine, ASPAC 116 set up for internal and external calls.

Any ideas why external trunk calls will not play the message?

We are at TSW SP6
 
show:

RAGAP:CORG=ALL;
RAMDP:ANN=ALL;
RADSP:VSID=ALL;

ASPAP:pARNUM=116;
ASPAP:pARNUM=161;
ASPAP:pARNUM=168;
ASPAP:pARNUM=169;

/Daddy




-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Note: This is U.S application

<RAGAP:CORG=ALL;
CORG ANNOUNCEMENT DATA
CORG WELCOM QUEUE CONT REPQUE QTIME RTIME
1 1 2 251 2 5 20
2 1 2 251 2 5 20
10 1
END

<RAMDP:ANN=ALL;
RECORDED VOICE ANNOUNCEMENT MESSAGE DATA
ANN MSG EWT
1 1
2 2

END

<RADSP:VSID=ALL;
NOT ACCEPTED
ANN
MISSING
<ASPAP:pARNUM=116;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
116 63
END
<ASPAP:pARNUM=161;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
161 0
END
<ASPAP:pARNUM=168;
NOT ACCEPTED
PARNUM
NOT IN SYSTEM
<ASPAP:pARNUM=169;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
169 3
END

<opctp:CORG=ALL;
OPERATOR CALL TYPE DATA
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP TIME OFLNUM SDAY SNIG
1 3 - 200 - N - N N - - - -
2 5 70 - - N - N N - - - -
3 6 60 500 - N - N N - - - -
10 5 1 - - N - N N - - - -

END

<opcgP:DIR=ALL;
OPERATOR CALL ORIGIN GROUP DATA
DIR
1
8
0
CORG -
1 1
2 1
3 1
10 1

END

<roDDP:DEST=ALL;
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
80 1 000500000000025000000000000 0 3 0
85 60 200500000000025000000000011 0 3 0
86 70 200500000000025000000000011 0 3 0

END

<rocap:ROU=ALL;
ROUTE CATEGORY DATA
ROU SEL TRM SERV NODG DIST DISL TRAF SIG BCAP
1 7130000000000010 6 3100030000 0 30 128 03151515 111110010000 001100
60 7110000000000010 4 2100000001 0 30 128 03151515 111100000031 111100
70 7130000000000010 4 2100000001 0 30 128 03151515 111100000031 111100

END

<rodap:ROU=ALL;
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
1 TL1 H'00000002 H'00000001 H'00000001 NO
60 SL60 H'00000300 H'15400000 H'00410000 NO
70 SL60 H'00000300 H'15400000 H'00310000 NO

END

<opcap:dIR=ALL;
OPERATOR CATEGORY DATA
DIR OPC PRG TRAF TRM
180 00000 1 1515 0

END
 
<radsp:ann=all;
RECORDED VOICE ANNOUNCEMENT DEVICE SELECTION DATA
ANN VSID EMDEV
1 1
2 1

END
 
I work with lcns, so the printout above is from the system with VSU issues.

<cnbip:bpos=1-0-00;

DEVICE BOARD REVISION INFORMATION
DATE: 24JUN09 TIME: 11:06:43

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND

001-0-00 85 CAA1122644 R4A01

END
 
What we are trying to accomplish is to be able to see who's calling before answer, thus the looped TLU76, we then assign names to the trunk with OPRSC. The RVA works fine for internal calls but we also need it to give a welcome message when they dial to the operator via the TLU76.

I just changed around with the CORGS again but the RVA will not kick in. Is there any other way we can get calling id before answer on OWS?

<raGAP:CORG=all;
CORG ANNOUNCEMENT DATA
CORG WELCOM QUEUE CONT REPQUE QTIME RTIME
1 1 2 251 2 5 20
2 1 2 251 2 5 20
3 1 2 251 2 5 20
4 1 2 251 2 5 20
5 1 2 251 2 5 20
END

<opctp:CORG=ALL;
OPERATOR CALL TYPE DATA
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP
1 1 - 0 - N - N N - - - -
2 2 - 0 - N - N N - - - -
3 3 - 0 - N - N N - - - -
4 4 70 - - N - N N - - - -
5 5 60 - - N - N N -

END

<opcgp:DIR=ALL;
OPERATOR CALL ORIGIN GROUP DATA
DIR
1
8
0
CORG -
1 1
2 1
3 1
4 1
5 1

END
 
the key problem is that you are not providing false B-answer (aspac 161)

use these settings:

ASPAC 139=1
ASPAC 138=5
ASPAC 161=8191

/Daddy




-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
I've changed the ASPAC's, still no go
I also tried to change d18 in ADC and d4 in sig.

<ASPAP:pARNUM=161;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
161 8191
END
<aspap:parnum=139;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
139 1
END
<ASPAP:pARNUM=138;
APPLICATION SYSTEM PARAMETERS
PARNUM PARVAL
138 5
END
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top