incomming CID problem

[Orintas]

When people call our office we see the number (CID), but not correct. We see doubled number - calling number and called number (number of our office line) jointly.
We use IP office 500, with Avaya IP phones. Incomming lines are conected trought analog trunk card, we using PSTN lines.
Analogue option\trunk type "loop start ICLID" is selected.
When i connect analog phone, incomming number is showed corect.

 

[kwing112000]

Maybe look at your incomming call routes. look for call tags. also do the lines come thru the voicemail before they are answered.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[Orintas]

incomming route is simple, just forward to extension, and any voicemail is not used.

 

[Orintas]

this is log from monitor:
9849013mS CMLineRx: v=2
CMSetup
Line: type=AnalogueLine 2 Call: lid=2 id=3 in=1
Called[] Type=Unknown (0) Reason=CMDRdirect SndComp Calling[865222335852762409] Type=Unknown Plan=Unknown Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=1 chan=2
IE CMIEDeviceDetail (231) LOCALE=eng HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=2 channel=0 gain=32
Timed: 22/00/08 11:11
9849013mS CD: CALL: 2.3.1 State=0 Cut=1 Music=0.0 Aend="Line 2" (1.2) Bend="" [] (0.0) CalledNum= () CallingNum=865222335852762409 () Internal=0 Time=5 AState=0
9849014mS CMTARGET: 2.3.1 13 Alog Trunk:2: LOOKUP CALL ROUTE: type=0 called_party= sub= calling=865222335852762409 in=1 complete=1 ses=0
9849014mS CMTARGET: INCOMING EXTERNAL CALL ROUTE
9849014mS CMTARGET: 2.3.1 13 Alog Trunk:2: SET BESTMATCH: length 0 vs 2 match= dest=599
9849014mS CMTARGET: 2.3.1 13 Alog Trunk:2: LOOKUP INCOMING CALL ROUTE: calling party is 865222335852762409. Matched profile Destination 599
9849014mS CMTARGET: 2.3.1 13 Alog Trunk:2: ADD TARGET (N): number=599 type=0 depth=1 nobar=1 setorig=1 ses=0
9849015mS CMTARGET: 2.3.1 13 Alog Trunk:2: FoundKnownSystemTargets 599 (ses: 0)
9849015mS CMTARGET: 2.3.1 13 Alog Trunk:2: SET USER: FAX orig=1
9849015mS CMTARGET: 2.3.1 13 Alog Trunk:2: ADD USER: FAX depth=2 disallow_cw=0 dnd=0 real_call=1 type(CMNTypeUnknown) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000
9849017mS CMTARGET: 0.1215.0 13 FAX.0: ADD PRIMARY
9849018mS PRN: BasicFindBestInCallRouteMatch returns(2)
9849018mS CMTARGET: 2.3.1 13 Alog Trunk:2: INITIAL TARGETING SUCCEEDED
9849018mS CMTARGET: 2.3.1 13 Alog Trunk:2: GetNoAnswerTimer:15
9849019mS CMLineTx: v=2
CMProceeding
Line: type=AnalogueLine 2 Call: lid=2 id=3 in=1
9849021mS CMExtnTx: v=599, p1=0
CMSetup
Line: type=AnalogueExtn 3 Call: lid=0 id=1 in=0
Called[599] Type=Unknown (0) Reason=CMDRdirect SndComp Calling[865222335852762409] Type=Unknown Plan=Unknown Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=2 chan=9
IE CMIEDeviceDetail (231) LOCALE=eng HW=8 VER=4 class=CMDeviceAlogTrunk type=0 number=2 channel=0 gain=32
IE CMIECalledPartyName (224) FAX
IE CMIEIcrPriorityDetail (239) Priority = 1
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:0 R:4) number=865222335852762409
UUI type=Local [......2Pd.] [0x01 0x01 0x00 0x00 0x01 0x02 0x32 0x50 0x64 0x00 ]
Display [External]
Timed: 24/04/08 14:10
Locale: eng
9849022mS CD: CALL: 2.3.1 State=0 Cut=1 Music=0.0 Aend="Line 2" (1.2) Bend="" [FAX(599)] (0.0) CalledNum=599 (FAX) CallingNum=865222335852762409 () Internal=0 Time=14 AState=8
9849024mS CMExtnRx: v=599, p1=0
CMAlerting
Line: type=AnalogueExtn 3 Call: lid=0 id=1 in=0
9849026mS CMLineTx: v=2
CMAlerting
Line: type=AnalogueLine 2 Call: lid=2 id=3 in=1
IE CMIERespondingPartyName (228) FAX
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=599
IE CMIEDeviceDetail (231) LOCALE=eng HW=8 VER=4 class=CMDeviceStdPhone type=3 number=25 channel=0 gain=32
9849026mS CD: CALL: 2.3.1 State=1 Cut=1 Music=2.0 Aend="Line 2" (1.2) Bend="" [FAX(599)] (0.0) CalledNum=599 (FAX) CallingNum=865222335852762409 () Internal=0 Time=18 AState=1
9849027mS PRN: Windowed EchoCancellation started: chunnel=1, command= 0x8401
9849028mS CMMap: a=1.2 b=0.0 R1
9854197mS RES: Thu 24/4/2008 14:10:58 FreeMem=79768528(11) CMMsg=5 (6) Buff=200 963 999 7198 5 Links=21432
9857651mS CMExtnRx: v=599, p1=0
CMConnect
Line: type=AnalogueExtn 3 Call: lid=0 id=1 in=0
9857651mS CMTARGET: 2.3.1 13 Alog Trunk:2: CancelTimer CMTCCoverageTimeout
9857652mS CMLineTx: v=2
CMConnect
Line: type=AnalogueLine 2 Call: lid=2 id=3 in=1
BChan: slot=2 chan=9
IE CMIERespondingPartyName (228) FAX
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=599
IE CMIEDeviceDetail (231) LOCALE=eng HW=8 VER=4 class=CMDeviceStdPhone type=3 number=25 channel=0 gain=32
9857653mS CMLineRx: v=2
CMConnectAck
Line: type=AnalogueLine 2 Call: lid=2 id=3 in=1
BChan: slot=1 chan=2
9857653mS CMTARGET: 2.3.1 13 Alog Trunk:2: ~CMTargetHandler
9857655mS CMExtnTx: v=599, p1=0
CMConnectAck
Line: type=AnalogueExtn 3 Call: lid=0 id=1 in=0
BChan: slot=2 chan=9
Timed: 24/04/08 14:11
9857655mS CD: CALL: 2.3.1 State=2 Cut=3 Music=0.0 Aend="Line 2" (1.2) Bend="FAX(599)" [FAX(599)] (2.9) CalledNum=599 (FAX) CallingNum=865222335852762409 () Internal=0 Time=8647 AState=2
9857656mS CMMap: a=1.2 b=0.0 R0
9857657mS CMMap: PCG::MapBChan pcp[91]b1r0 cp_b f5ab9666 other_cp_b 0 type CGTypeSimple
9857657mS CMMap: PCG::MapBChan pcp[94]b1r0 cp_b f5ab667a other_cp_b f5ab9666 type CGTypeSimple
9857657mS CMMap: a=1.2 b=2.9 M1



"CallingNum=865222335852762409"
two numbers in one:
865222335 - calling number
852762409 - called number

 

[kwing112000]

Do you have any kind of prefix on the lines? does the called number change depending on the trunk the call is comming in on?

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[Orintas]

Do you have any kind of prefix on the lines? - No

 

[kwing112000]

What release is this running?

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[Orintas]

4.1

 

[kwing112000]

4.1.what?? there is 4.1.9 or 4.1.14.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[Orintas]

4.1 (9)

 

[kwing112000]

does it change when calling different trunks? or does it always show the main number? I have a customer that reported the caller id changed when we upgraded from 4.0 to 4.1 with IP phones. I have not looked at it. on your incomming call route do you just have the line group and the destination? is there anything else on the incomming call route? with POTS lines you should not have anything in the incomming sub address or incomming CLI. you could try to upgrade to 4.1.12 and see if it fixes it.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[Orintas]

i downloading now 4.1.12 version of admin CD, and wil try to upgrade .
On incomming call route incomming line group is directly forwardet to extension. time profiles are not used, just forward to extension.
From SIP trunk all ICLID's are showed correct. This isue is only with analog trunks.
after upgrade, if this helps, i will post here answer.
thanks for all.

 

[Orintas]

hi,
i have upgradet my IP office system to 4.1(12).
my problem with incomming CID still exist.

 

[Bas1234]

Wat did you fill in in the incomming call route?

You only need to fill in the "incomming number" "line group ID" and the "destination".

Greetzzz...Bas

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[Orintas]

only these fields are filled in

 

[Bas1234]

What are the line settings?

Did you try to select "Loop Start"?

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________