E******* Alerting message duration

[slavicp]

Hello,
Could somebody help me on the following issue:
I need to find the timer that is in charge for duration of ring back tone (Alerting message) in e******* AXE10 exchange.
The problem is that in the internal network it is set for example to 40 sec., but I want to find out if there is possible to change it for a certain Route, etc.
thanks,
BR,
slavicp

[roloramos]

Try to find the answer in this docs...

[milan_recj]

Part of document is not in English. If you have this in English kindly upload.

[roloramos]

Try to find the answer in this docs...


Unfortunately i dont have other version....Sorry

[slavicp]

Thanks friend, but I didn't find the parameter that is responsible for duration of RBT yet...

[scorpiobgd]

Do you need information about Personal Ring Back Tone or ordinary ring back tone.... ? I found some timers in alex but i dont know what you need....

[slavicp]

I need for ordinary ring back tone... I supose that there must be some parameter in axepars related to the duration of ring back tone, actually in our network is set for example to 30 sec max and after it if the B subscriber doesn't answer in this time the call is released. I'd like to know if there is any posibility to set this timer for example 60 sec on a specified route only or it is global parameter? I want to increase this timer on a interconection with a PBX.

[slavicp]

I need for ordinary ring back tone... I supose that there must be some parameter in axepars related to the duration of ring back tone, actually in our network is set for example to 30 sec max and after it if the B subscriber doesn't answer in this time the call is released. I'd like to know if there is any posibility to set this timer for example 60 sec on a specified route only or it is global parameter? I want to increase this timer on a interconection with a PBX.

[scorpiobgd]

Ok... I see... You cannot set this parameter for route because it is an global parameter...(for signaling type for example, bssap, isup, bicc and other). In other case you can do some analysis like time supervision analysis on routing case combined with eos analysis....

[slavicp]

Ok, But i'd like to find out what is the parameter in charge of the duration of ring back tone (after that the call is released if the B subscriber doesn't answer)?
I have change it for PRA connection...

[scorpiobgd]

Function block TRATS is a part of the Traffic Control Subsystem (TCS) in the Transit AM (TRAM).

Block TRATS takes care of the following supervisions during a call:

Call set-up time
B-answer time
Network initiated suspend time
Long duration calls
Block TRATS is also responsible for trunk offering.

[scorpiobgd]

NSYMB SETUPSUPT = 120;
! VALUE RANGE: 0-255 !
! SOURCE PARAMETER DESCRIPTION: !
! VALUE RANGE: 0-255 !
! GUIDING VALUE: 120 !
! CALL-SETUP SUPERVISION TIME IN !
! SECONDS. !
! THE INTERVAL GUARDED BY 'TIME SUPER- !
! VISION BEFORE B-ANSWER' IS NOT TAKEN !
! INTO ACCOUNT. !
! THE CANCELLATION OF TIME SUPERVISION !
! TAKES PLACE WITH THE VALUE 0. !
! NOTE: THE TIME MEASUREMENT OF CALL- !
! SETUP TIME WILL NOT BE !
! CORRECT WHEN NO TIME !
! SUPERVISION IS TAKING PLACE AND !
! THE CALL-SETUP TIME !
! IS MORE THAN 127 SECONDS. !
! !
! !

[scorpiobgd]

i hope so this was useful for you.... you must do this by setvar...

[slavicp]

Hi scorpiobgd,
Many thanks for this info it is really useful, as I understand the parameter related to duration of RBT (NSYMB SETUPSUPT) we can printout/set it only with test system, or we can see it also for example in axepars with DBTSC command?
BR,
slavicp

[scorpiobgd]

this is plex busines... if you know to work, analyse and set variables in software blocks you will resolve this... but I think that is the question for second line eric support... actualy I cant help You becouse Im not plex expert... :-( in one word, this not configurable by operator (with dbtsc AXEPARS command)

[slavicp]

Ok, thanks for your answer!

[slavicp]

BTW, how to printout this variable: print var ...???

[scorpiobgd]

I think so... print var...

[slavicp]

yes, but what parameters, pointers to printout... for example: "print var NSYMB SETUPSUPT;" or print var SETUPSUPT;" is incorect, not working...

[scorpiobgd]

I¸am allready looking for information about this... you must do test system and print var for trats block... i hope so I will soon get answer which variable is pointed to this parameter... regards...

[scorpiobgd]

which is software rel of your msc ?

[scorpiobgd]

for rel 13.2

TEST SISTEM;

PRINT VAR TRATS 69(0-);

Be careful.. :-)

[slavicp]

the release is R12