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

No Incoming CLI number in Analog trunk call while using GSM Gateway IPO9.0.1

Status
Not open for further replies.

iramipo

Programmer
Nov 21, 2013
82
IN
Hi Everyone,

i am struggling with the CLI issue found with Analog trunk line which is connected from a GSM Gateway. The GSM gateway shows the incoming number, and a analog phone which is connected back with GSM GW shows the Cli number. But ipoffice is not showing in systems status and 14xx phones/analog phones.

below the trace output:
406040mS ATMChannel: [1] DTMF Message Rx: 0x0000 (Tone=0x0000)
406175mS ATMChannel: [1] DTMF Message Rx: 0x0140 (Tone=0x0005)
406320mS ATMChannel: [1] DTMF Message Rx: 0x0000 (Tone=0x0000)
406460mS ATMChannel: [1] DTMF Message Rx: 0x0100 (Tone=0x0004)
410065mS ATMChannel: [1] External Rx: 'IncomingRing' (ls)
410065mS ATMChannel: [1] StateChange Idle->CLIPossibleIncoming
410115mS ATMChannel: [1] Sloppy timeout(50ms)
410145mS ATMChannel: [1] StateChange CLIPossibleIncoming->CLIAwaitData
410145mS ATMChannel: [1] CMLinkLayer Tx: 'Alert_PreIndication'
410146mS ATMCMLine: [1] CMLinkLayer Rx: 'Alert_PreIndication' callid=(lid=1, id=0, in=1)
410146mS ATMCMLine: [1] StateChange Idle->IncomingGuard
415145mS ATMChannel: [1] Sloppy timeout(5000ms)
415145mS ATMChannel: [1] StateChange CLIAwaitData->CLIAwaitSecondRing
416225mS ATMChannel: [1] StateChange CLIAwaitSecondRing->PossibleIncoming
416725mS ATMChannel: [1] Sloppy timeout(500ms)
416745mS ATMChannel: [1] StateChange PossibleIncoming->Incoming
416745mS ATMChannel: [1] CMLinkLayer Tx: 'Ringing'
416746mS ATMCMLine: [1] CMLinkLayer Rx: 'Ringing' callid=(lid=1, id=0, in=1)
416746mS ATMCMLine: [1] StateChange IncomingGuard->Present
416746mS ATMCMLine: [1] IncomingCall
416750mS CMTARGET: 1.2.1 10 Alog Trunk:1: LOOKUP CALL ROUTE: type=0 called_party= sub= calling= dir=in complete=1 ses=0
416751mS CMTARGET: 1.2.1 10 Alog Trunk:1: SET BESTMATCH: length 0 vs -1 match=7660019444 dest=AA:KKPWelcome
416751mS CMTARGET: 1.2.1 10 Alog Trunk:1: AMBIGUITY: match=7661975111 dest=AA:KKPWelcome
416751mS CMTARGET: 1.2.1 10 Alog Trunk:1: LOOKUP ICR: DDI= CGPN= (Destination AA:KKPWelcome ) => CDPN=AA:KKPWelcome
416751mS CMTARGET: 1.2.1 10 Alog Trunk:1: ADD TARGET (N): number=AA:KKPWelcome type=0 depth=1 nobar=1 setorig=1 ses=0
416751mS CMTARGET: 1.2.1 10 Alog Trunk:1: ADD VM TARGET
416752mS CMTARGET: **** 1.2.1 10 Alog Trunk:1: MakeVoicemailTarget pbx=<null> local=1 type=3
416752mS CMTARGET: 0.1028.0 10 RAS.0: ADD PRIMARY
416752mS CMTARGET: 1.2.1 10 Alog Trunk:1: ADD VM TARGET: SUCCEEDED
416753mS CMTARGET: 1.2.1 10 Alog Trunk:1: INITIAL TARGETING SUCCEEDED
416753mS CMTARGET: 1.2.1 10 Alog Trunk:1: GetNoAnswerTimer:15
416753mS ATMCMLine: [1] ControlEchoCancellation ON
416754mS ATMCMLine: [1] CMLinkLayer Tx: 'EchoControl'
416754mS ATMCMLine: [1] StateChange Present->ICProceeding
416758mS CMTARGET: 1.2.1 10 Alog Trunk:1: CancelTimer CMTCNoAnswerTimeout
416759mS ATMCMLine: [1] ControlGainAdjust 2
416759mS ATMCMLine: [1] CMLinkLayer Tx: 'IncrementGain'
416760mS CMTARGET: 1.2.1 10 Alog Trunk:1: ~CMTargetHandler f4c18110 ep f4bf61a8
416764mS ATMChannel: [1] CMLinkLayer Rx: 'EchoControl' (ls)
416764mS ATMIO: [1] ECHO CANCELLATION ON
416764mS ATMChannel: [1] CMLinkLayer Rx: 'IncrementGain' (ls)
416789mS ATMCMLine: [1] StateChange ICProceeding->ConnReq
416789mS ATMCMLine: [1] CMLinkLayer Tx: 'Answer'
416789mS ATMChannel: [1] CMLinkLayer Rx: 'Answer' (ls)
416790mS ATMIO: [1] BLOCK FORWARDING OFF
416790mS ATMIO: [1] TRUNK SEIZE
416790mS ATMChannel: [1] CMLinkLayer Tx: 'AnswerAck'
416790mS ATMChannel: [1] StateChange Incoming->Connected
416790mS ATMIO: [1] CLI DETECTION OFF, EQUALISER OFF
416790mS ATMIO: [1] BLOCK FORWARDING ON
416791mS ATMCMLine: [1] CMLinkLayer Rx: 'AnswerAck' callid=(lid=1, id=2, in=1)
416791mS ATMCMLine: [1] StateChange ConnReq->Active
416791mS ATMCMLine: [1] CM Tx: 'CMConnectAck' callid=(lid=1, id=2, in=1)
417290mS ATMChannel: [1] Sloppy timeout(500ms)
417290mS ATMIO: [1] BLOCK FORWARDING OFF
437821mS CMTARGET: 0.1029.0 11 RAS.1: LOOKUP CALL ROUTE: type=100 called_party=3535 sub= calling= dir=out complete=0 ses=0
437821mS CMTARGET: 0.1029.0 11 RAS.1: ADD TARGET (N): number=3535 type=100 depth=1 nobar=1 setorig=1 ses=0
437821mS CMTARGET: 0.1029.0 11 RAS.1: SET USER: OperatorKKP orig=1
437822mS CMTARGET: 0.1029.0 11 RAS.1: ADD USER: OperatorKKP depth=1 disallow_cw=0 dnd=0 real_call=1 group_call=0 type(CMNTypeDefault) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000 simult 0 (0)
437823mS CMTARGET: 0.1031.0 11 OperatorKKP.0: ADD PRIMARY
437823mS CMTARGET: 0.1029.0 11 RAS.1: CancelTimer CMTCDialToneTimeout
437823mS CMTARGET: 0.1029.0 11 RAS.1: INITIAL TARGETING SUCCEEDED
437824mS CMTARGET: 0.1029.0 11 RAS.1: GetNoAnswerTimer:15
437853mS CMTARGET: TransferProposal: X_call: ID=11 Aend= -> 3535
437853mS CMTARGET: TransferProposal: Y_call: ID=10 Aend= -> #AA:KKPWelcome
437853mS CMTARGET: Surviving Call=10
437853mS CMTARGET: Goodbying Call=11
437853mS CMTARGET: AEND -> 3535 BEND
437858mS CMTARGET: 0.1029.0 11 RAS.0: ChangeOriginator: To 1.2.1 10 Alog Trunk:1

Any thing has to be chaged here?

Thanks
iramipo
 
Then the GSM gateway use a CLI protocol not recognized by IP Office. Try to change it in the GSM box or Buy a ISDN/SIP GSM gateway.
 
Thanks @intrigrant..

Is there any other possibilities ?? with the same GSM gateways..
 
Try This.

Manager> Line> Analogue Options

· Long CLI Line: Default = Off
The CLI signal on some analog lines can become degraded and is not then correctly detected. If you are sure that CLI is being provided but not detected, selecting this option may resolve the problem.


Dulce et decorum pro Avaya mori
 
Long CLI is already enabled.

But not receiving any CLI info on that line.
 
with the same GSM gateways..

An idea on what GSM gateways would be useful, but you knew that right?


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
I wonder:
406040mS ATMChannel: [1] DTMF Message Rx: 0x0000 (Tone=0x0000)
406175mS ATMChannel: [1] DTMF Message Rx: 0x0140 (Tone=0x0005)
406320mS ATMChannel: [1] DTMF Message Rx: 0x0000 (Tone=0x0000)
406460mS ATMChannel: [1] DTMF Message Rx: 0x0100 (Tone=0x0004)
IP Office receive as DTMF 0405, is that the expected CLI?
 
Hi @mattKnight,
We are having Visiontek 81g FCT device.

Hi @intrigrant,
infact all the dtmf messages showing the exact CLI number, it is 91XXXXXX0504 as you pasted above.

but in the System status i'm not getting CLI, instead it is None.

Any other options??
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top