Alcatel Unleashed

Hi All

OXE R8.0

One of our customers is having a problem with External calls to Hunt Groups. When an External call is made to a Hunt Group (Directly to Hunt Group Nr. not the members) a tone is played before the members are rung.

Senario: External call -> Tone is playing for 4-5 sec (sound like a normal ofhook tone) -> members are ringing.

The members does NOT ring while the tone is played. This problem is happening on all Hunt Groups.

I cant remember seeing a feature that puts a tone in front of a Hunt Group? And I have checked its not a VG.

Is there a command like the vgemis just for tones so i can see whitch one is playing?

Any help would be highly appreciate!!

Best Regards

In your case - you have usual external calls via digital line (DID translator and so on)? Automatic attendant, DISA, CDT entity, incoming call greeting guide not used?

Yes ISDN T2 + DID trans.

No Auto. Att CDT and Incoming Greet.

Just as a test I have tried to: External call -> UA fictive forwarded to HG -> Hunt group. Makes no diffrence.

Local calls to the Hunt group have no problems.

Check with t3 trace:
- when external user hear "on-hook tone" - PBX send CONNECT or ALERT?
- when HG users start ring - PBX send something or not?

Compare with trace for normal calls - external calls to usual user.

Hi Vad,

There is the trace:

______________________________________________________________________________
| (990803:000002) Physical-Event :
| long: 52 desti: 0 source: 0 cryst: 1 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : SETUP [05] Call ref : 6e 1f
|______________________________________________________________________________
|
| IE:[04] BEARER_CAPABILITY (l=3) 80 90 a3
| IE:[18] CHANNEL (l=3) a9 83 93 -> T2 : B channel 19 exclusive
| IE:[6c] CALLING_NUMBER (l=10) -> 21 83 Num : 123456789
| IE:[70] CALLED_NUMBER (l=9) -> a1 Num : 123456789
| [a1] Sending complete
|______________________________________________________________________________

______________________________________________________________________________
| (990803:000003) 1064: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 23 desti: 0 source: 15 cryst: 1 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CALL PROC (02) Call ref : ee 1f
|______________________________________________________________________________
|
| IE:[18] CHANNEL (l=3) a9 83 93 -> T2 : B channel 19 exclusive
|______________________________________________________________________________

______________________________________________________________________________
| (990803:000004) 1064: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 22 desti: 0 source: 15 cryst: 1 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : ALERT (01) Call ref : ee 1f
|______________________________________________________________________________
|
| IE:[1e] PROGRESS_ID (l=2) 81 88
|______________________________________________________________________________

______________________________________________________________________________
| (990807:000005) 1064: Send_IO1 (link-nbr=1, sapi=0, tei=0) :
| long: 18 desti: 0 source: 15 cryst: 1 cpl: 9 us: 8 term: 0 type a5
| tei: 0 <<<< message sent : CONNECT (07) Call ref : ee 1f
|______________________________________________________________________________

______________________________________________________________________________
| (990808:000006) Physical-Event :
| long: 18 desti: 0 source: 0 cryst: 1 cpl: 9 us: 0 term: 0 type a5
| tei: 0 >>>> message received : CONNECT ACK (0f) Call ref : 6e 1f
|______________________________________________________________________________

When HG users start ring - nothing more is sendt out

Looks like some moments with - TG local parameters item "VG for non-existent No." or System/ other system - item "Cx on Progress message".
You system send CONNECT before call distribution and try to send some VG (calling user hear backup tone from VG).

Hi Vad,

I finally found the error. We had some errors in prefixes that pointed to VG numbers with no working VG.

Thx for helping!

Best Regards

incoming call greeting guide?

Yes