Changed to a 406 V2 outgoing CLI has stoped working???

[bm97ppc]

Hi,

We had a 406 V2 with PRI60 card in the office so I decided to swap our current 403 Demo kit with it to try out some of the version 4.0 + improvements.

Anyway simple task, we use ISDN 2e so I added the card from out current system (PRI 60 Slot A BRI 8 Slot B) Upgraded the system from 3.2 to 4.2 (11) uploaded our config, all well and good.

Didn't notice any problems tell the next day, all calls out are using the main number CLI not there respective DDi’s so I did the following:

1) Check incoming call routes (yes DDi still inbound ok)
2) Notice you can have time profiles ICR so thought you may need to specify out going CLI in a user short code as it is now ‘Many to One’ (albeit only 1 to 1 on a time profile) tried short code still no luck, tested user short code withheld (.SW) that worked fine.
3) Downgraded to 3.2, still a problem
4) OK what's differene other then hardware?, so removed PRI60 leaving just BRI 8 in Slot B (how it was in 403), still no luck.
5) Upgraded back to 4.2 as run out of ideas,
6) had one last thought, blanked Config tested with the most basic config still main number going out.

So the only change not eliminated is the 406 v2 unfortunately our 403 when out as maintenance stock so I couldn't go back to the original setup to eliminate BT / the hardware (would be very unlucky for BT to mess up some thing at the exchange at exactly the same time I switch the PBX but then again it is BT).

Have I missed something or has anyone else had an outgoing DDI problem from a 406 V2?

Regards

Piers

 

[bm97ppc]

ok tried 4, still no joy

 

[mattKnight]

>Post a monitor trace of an outbound call, with ISDN trace turned on

This will tell us what you are sending...

Please also post a trace of a DDI call - this will tell us what BT are sending
I don't want reams of it jst the bits that look like this

69446309mS ISDNL1Rx: v=16 peb=16
0000 02 01 f8 20 08 01 01 05 a1 04 03 80 90 a3 18 01 ... ............
0010 89 6c 0c 21 83 37 39 38 30 36 31 32 35 30 36 70 .l.!.YYYYYYYYYYp
0020 07 81 30 37 34 37 31 31 ..XXXXXX
69446310mS ISDNL2Rx: v=16 peb=16
0000 02 01 f8 20 08 01 01 05 a1 04 03 80 90 a3 18 01 ... ............
0010 89 6c 0c 21 83 37 39 38 30 36 31 32 35 30 36 70 .l.!.YYYYYYYYYYp
0020 07 81 30 37 34 37 31 31 ..XXXXXX

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.

 

[bm97ppc]

Is this what you are after

I Called 08712309296

it was the only call on the system at the time.

We have 1 X BT ISDN 2e pluged into port 1 of slot A (AKA Line 5 in the IPO)

45370537mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 21 ...!
45370537mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 21 ...!
45370537mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 9f ....
45370541mS ISDNL1Tx: v=5 peb=5
0000 02 01 01 9f ....
45372241mS CMCallPkt: v=0
CMInformation
Line: type=IPLine 250 Call: lid=252 id=2 in=1
IE CMIECCMSMessage (5) unknown
45372242mS PRN: Piers: DSS Appearance Key Pressed 0
45372243mS CMCallEvt: 0.1118.0 -1 BaseEP: NEW CMEndpoint fecd4cf4 TOTAL NOW=1 CALL_LIST=0
45372243mS PRN: Created MH fecd4be8 parent 252.1118.0 -1 Piers.-1
45372244mS CMCallEvt: CREATE CALL:32 (fecbd7ec)
45372244mS CMCallEvt: 0.1119.0 -1 BaseEP: NEW CMEndpoint fed2182c TOTAL NOW=2 CALL_LIST=0
45372247mS CMExtnEvt: Piers: CMExtnHandler::SetCurrent( id: 0->1118 )
45372254mS CMCallEvt: 252.1118.0 32 Piers.0: StateChange: END=A CMCSIdle->CMCSDialInitiated
45372254mS CMExtnEvt: v=2 State, new=Connected old=Idle,0,0,Piers
45372258mS CMCallEvt: 252.1118.0 32 Piers.0: StateChange: END=A CMCSDialInitiated->CMCSDialling
45372258mS CMExtnEvt: v=2 State, new=Dialling old=Connected,0,0,Piers
45372263mS CMExtnTx: v=205, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=252 id=1118 in=0
IE CMIEFastStartInfoData (6)
Timed: 18/11/08 10:50
45372264mS CMExtnTx: v=205, p1=8001
CMFacility
Line: type=IPLine 250 Call: lid=252 id=2 in=1
IE CMIEFastStartInfoData (6)
45372264mS CMExtnTx: v=205, p1=0
CMSetupAck
Line: type=IPLine 250 Call: lid=252 id=1118 in=0
Timed: 18/11/08 10:50
45372289mS CMCallPkt: v=0
CMInformation
Line: type=IPLine 250 Call: lid=252 id=2 in=1
IE CMIECCMSMessage (5) unknown
45372737mS CMCallPkt: v=0
CMInformation
Line: type=IPLine 250 Call: lid=252 id=2 in=1
IE CMIECCMSMessage (5) unknown
45372737mS PRN: 205: Digit Pressed 0
45372747mS CMCallPkt: v=0
CMInformation
Line: type=IPLine 250 Call: lid=252 id=2 in=1
IE CMIECCMSMessage (5) unknown
45372953mS CMCallPkt: v=0
CMInformation

 

[bm97ppc]

maybe this is better:

45373116mS ISDNL3Evt: v=5 stacknum=5 State, new=Initiated, old=NullState id=1120
45373116mS ISDNL3Tx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=1 ref=0C(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 80 90 a3 .....
InformationElement = CallingPartyNumber
0000 6c 0c 00 80 32 30 38 35 38 39 37 38 34 34 l...2085897844
InformationElement = CalledPartyNumber
0000 70 04 80 30 38 37 p..087
45373117mS ISDNL2Tx: v=5 peb=5
0000 00 01 20 9e 08 01 0c 05 04 03 80 90 a3 6c 0c 00 .. ..........l..
0010 80 32 30 38 35 38 39 37 38 34 34 70 04 80 30 38 .2085897844p..08
0020 37 7
45373119mS ISDNL1Evt: v=8 peb=8,F4 F3
45373122mS ISDNL1Evt: v=6 peb=6,F4 F3
45373135mS ISDNL1Tx: v=5 peb=5
0000 00 01 20 9e 08 01 0c 05 04 03 80 90 a3 6c 0c 00 .. ..........l..
0010 80 32 30 38 35 38 39 37 38 34 34 70 04 80 30 38 .2085897844p..08
0020 37 7
45373143mS ISDNL1Rx: v=5 peb=5
0000 00 01 01 22 ..."
45373144mS ISDNL2Rx: v=5 peb=5
0000 00 01 01 22 ..."
45373245mS PRN: 205: Digit Pressed 1
45373290mS ISDNL1Rx: v=5 peb=5
0000 02 01 9e 22 08 01 8c 0d 18 01 89 ...".......
45373290mS ISDNL2Rx: v=5 peb=5
0000 02 01 9e 22 08 01 8c 0d 18 01 89 ...".......
45373290mS ISDNL3Rx: v=5 peb=5
ISDN Layer3 Pcol=08(Q931) Reflen=1 ref=0C(Local)
Message Type = SetupAck
InformationElement = CHI
0000 18 01 89 ...
45373290mS ISDNL3Evt: v=5 stacknum=5 State, new=OverlapSend, old=Initiated id=1120
45373291mS ISDNL2Tx: v=5 peb=5
0000 02 01 01 a0 ....
45373292mS CMCallPkt: v=0

 

[mattKnight]

You are sending 10 digits (2085897844) is that what you have currently programmed?




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.

 

[mattKnight]

also a trace of an incoming DID call to tell us how many digits you are getting from BT

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.

 

[jamie77]

If BT are sending you 6 digits for the DDI's then you need to send them 6 digits for CLI. I have seen it cause issues when this is not done.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!

 

[bm97ppc]

Yep it is 6, I have tried 6 still makes no diffrence, the current Config has worked for over 5 years we started with Version 1.4, I have downgraded to the last working firmware 3.2(54) still not working. the only change is the hardware 403 > 406 V2

0800028mS CMLineRx: v=5
CMSetup
Line: type=Q931Line 5 Call: lid=5 id=2 in=1
Called[897844] Type=Unknown (0) Reason=CMDRdirect SndComp Calling[07710023684] Type=National Plan=ISDN Pres=Allowed (0)
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=2
50800028mS PRN: Q931Trunk: Found QBChannel to match 0.2 --> 7.2
50800029mS CMCallEvt: 0.1164.0 -1 BaseEP: NEW CMEndpoint fecbb930 TOTAL NOW=1 CALL_LIST=0
50800029mS CMCallEvt: CREATE CALL:46 (fed22808)
50800030mS CMCallEvt: 0.1165.0 -1 BaseEP: NEW CMEndpoint fed2182c TOTAL NOW=2 CALL_LIST=0
50800034mS CD: CALL: 5.2.1 BState=Idle Cut=1 Music=0.0 Aend="Line 5" (7.2) Bend="" [] (0.0) CalledNum=897844 () CallingNum=07710023684 (Piers Mobile) Internal=0 Time=5 AState=Idle
50800035mS CMCallEvt: 5.2.1 46 Q931 Trunk:5 CHAN=2: StateChange: END=A CMCSIdle->CMCSDialInitiated
50800036mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: LOOKUP CALL ROUTE: type=0 called_party=897844 sub= calling=07710023684 dir=in complete=1 ses=0
50800036mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: SET BESTMATCH: length 0 vs 0 match= dest=ETS
50800037mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: SET BESTMATCH: length 6 vs 0 match=2085897844 dest=205
50800037mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: LOOKUP ICR: DDI= CGPN=07710023684 (Destination 205 ) => CDPN=205
50800038mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: ADD TARGET (N): number=205 type=0 depth=1 nobar=1 setorig=1 ses=0
50800038mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: SET USER: Piers orig=1
50800038mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: ADD USER: Piers depth=2 disallow_cw=0 dnd=0 real_call=1 type(CMNTypeUnknown) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000
50800039mS CMMap: a=3.1 b=0.0 Mapper::AllocateCodec allocated CMRTVocoder resource busy 1, total 10
50800040mS CMCallEvt: 0.1166.0 -1 BaseEP: NEW CMEndpoint fecd1af4 TOTAL NOW=3 CALL_LIST=1
50800040mS PRN: Created MH fecd19e8 parent 252.1166.0 -1 Piers.-1
50800042mS CMTARGET: 252.1166.0 46 Piers.0: ADD PRIMARY
50800043mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: INITIAL TARGETING SUCCEEDED
50800043mS CMTARGET: 5.2.1 46 Q931 Trunk:5 CHAN=2: GetNoAnswerTimer:15
50800043mS CMCallEvt: 5.2.1 46 Q931 Trunk:5 CHAN=2: StateChange: END=A CMCSDialInitiated->CMCSDialled
50800044mS CMLineTx: v=5
CMProceeding
Line: type=Q931Line 5 Call: lid=0 id=2 in=1
BChan: slot=0 chan=2
50800045mS CMCallEvt: 0.1165.0 46 TargetingEP: StateChange: END=B CMCSIdle->CMCSOffering
50800046mS CMCallEvt: 252.1166.0 46 Piers.0: StateChange: END=T CMCSIdle->CMCSOffering
50800049mS CMExtnEvt: Piers: CMExtnHandler::SetCurrent( id: 0->1166 )
50800049mS CMExtnTx: v=205, p1=0

 

[mattKnight]

50800034mS CD: CALL: 5.2.1 BState=Idle Cut=1 Music=0.0 Aend="Line 5" (7.2) Bend="" [] (0.0) CalledNum=897844 () CallingNum=07710023684 (Piers Mobile) Internal=0 Time=5 AState=Idle

I make that 6 digits inbound.

Ok Start very simply (assumes you don't have an 8 prefix anywhere)

User shortcode
SC - 8N
Feat - Dial
TN - NS<6digitsvalidDDI>
LG - 0

test by dialling 8 then your mobile

if that works, move the shortcode to the System shortcodes. if it doesn't, try again and post the ISDN log

If that works change the Linegroup to 50 and try again. if it doesn't, try again and post the ISDN log

Finally look at the ?/./dial shortcode in the ARS






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.

 

[bm97ppc]

OK Tried the above on difference, had all but given up. Finally the Answer; called a mobile and they called back on my DDI ??????? How????

Call my mobile sill the same, called a college on a non work mobile(O2) DDI went out. Bingo All my test were to work mobiles (Orange). It seems that orange are sending the Originating Number as CLI, they happen to change this at the same time i switched PBX, HOW ANOYING. I haven't spoke to orange yet. Anyone else spotted this?

Thanks for everyone’s suggestions

Piers

 

[TomMills]

yea, happens all the time, not sure why.

i usually see it where they press to call back from voicemail

not found a fix yet, orange will say they show what they are given, BT will say they send what you send.

 

[mattKnight]

>not found a fix yet, orange will say they show what they are given, BT will say they send what you send.


I'd trust orange slightly less than BT. We had dreadful issues with our customers being unable to call orange phones because the orange network would only accept calls at Speech 3K1 capability

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.

 

[TomMills]

really? what happened when they tried to dial an orange number?

 

[mattKnight]

Failed to 3 note & BT message - Service not compatible. I think...

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.

 

[amriddle01]

Me too Tom, we have a customer who gets calls on the Main line number when they advertise their own DDI's, after MUCH testing we found that certain Mobile providors I think Orange was one of them do in fact call the main bearer number from voicemail not the DDI you advertise.

ACS - IP Office Implement

 

[TomMills]

its a pig troubleshooting for the first time. everytime they dialed my mobile i saw the ddi presented so i wrote it off as a customer "moment"

but turns out some mobile providers screw it up. happens when i get off the tube, because i am on orange i get a text saying who rang but didnt leave a voicemail. if anyone in our office rings me it shows the bearer numbr, i never know who it is

 

[amriddle01]

This means that BT must send the bearer number and the DDI otherwise how does it know the bearer number? If they sent just the DDI that is all they could show...I don't know how things work in the exchange and beyond, suppose I never will.

ACS - IP Office Implement

 

[TomMills]

i walk past our exchange on my way to the station every morning, i keep wanting to knock on the door and have a look around, see what goes on behind the scenes, but i think they might section me

 

[amriddle01]

It is all just Routers broke out onto Krone fields (huge ones) as I understand, have no clue how they program them mind.

ACS - IP Office Implement

 

[mattKnight]

> but i think they might section me

I think you'd also have to sign the Official Secrets Act...

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.