9.1.4 PRI Add numbers to inbound ddi

[daken]

Can anyone guess where the additionl 0 has come from?
we normaly programm the inbound call route with the full nation number without leading 0. (UK ISDN30 from BT)
we upgraded our office then found the extra 0 geting prepended to the inbound ddi breaking our inbound routes

who Thinks this is a bug?
[pre]

13:41:08 245267348mS ISDNL3Rx: v=13 peb=13
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0002(Remote)
Message Type = Setup
InformationElement = Sending Complete
InformationElement = BearerCapability
0000 04 03 90 90 a3 .....
InformationElement = CHI
0000 18 03 a9 83 82 .....
InformationElement = PI
0000 1e 02 84 83 ....
InformationElement = CalledPartyNumber
0000 70 07 a1 36 35 30 30 38 33 p..[highlight #FCE94F]650083[/highlight]
13:41:08 245267348mS ISDNL3Evt: v=13 stacknum=13 State, new=Present, old=NullState id=11
13:41:08 245267349mS CMCallPkt: v=0
CMSetup
Line: type=Q931Line 13 Call: lid=0 id=11 in=1
Called[[highlight #FCE94F]650083[/highlight]] Type=National (2) Reason=CMDRdirect SndComp Calling[] Type=Unknown Plan=Default Pres=NAInterworking (2)
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=2
IE CMIEProgressIndicator (30) cs=CMCSITUT (0), loc=CMLPublicNetRemoteUser (4), pd=CMPDOrigNotISDN (3)
13:41:08 245267349mS CMLineRx: v=13
CMSetup
Line: type=Q931Line 13 Call: lid=13 id=11 in=1
Called[[highlight #FCE94F]0650083[/highlight]] Type=National (2) Reason=CMDRdirect SndComp Calling[] Type=Unknown Plan=Default Pres=NAInterworking (2)
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=2
IE CMIEProgressIndicator (30) cs=CMCSITUT (0), loc=CMLPublicNetRemoteUser (4), pd=CMPDOrigNotISDN (3)
13:41:08 245267349mS PRN: Q931Trunk: Found QBChannel to match 0.2 --> 7.3
13:41:08 245267350mS CMCallEvt: 0000000000000000 0.7322.0 -1 BaseEP: NEW CMEndpoint f1871fc4 TOTAL NOW=3 CALL_LIST=1
13:41:08 245267350mS CMCallEvt: CREATE CALL:1620 (f16f05c0)
13:41:08 245267350mS CMCallEvt: 0000000000000000 0.7323.0 -1 BaseEP: NEW CMEndpoint f173d62c TOTAL NOW=4 CALL_LIST=1
13:41:08 245267352mS CD: CALL: 13.11.1 BState=Idle Cut=1 Music=0.0 Aend="Line 13" (7.3) Bend="" [] (0.0) CalledNum=[highlight #FCE94F]0650083[/highlight] () CallingNum= () Internal=0 Time=2 AState=Idle
13:41:08 245267352mS CD2: CALL:S 13.11.1,0.7323.0,0,0,1,0,0,0,Line 13,,,7.3,0.0,100.2,[highlight #FCE94F]0650083[/highlight],2.0,,,,100,,100,,0,16,0,1,16.0,,,,,,,0,2,0,0,0,0,,,0,,0,0,0,0,,1620,0,0,,0,,3,0,0,0,0,0,0,1,618,1,,,,,,,,,,,,,,,
13:41:08 245267352mS CMCallEvt: 0a8d90fe0000000b 13.11.1 1620 Q931 Trunk:13 CHAN=2: StateChange: END=A CMCSIdle->CMCSDialInitiated
13:41:08 245267353mS CMTARGET: 0a8d90fe0000000b 13.11.1 1620 Q931 Trunk:13 CHAN=2: LOOKUP CALL ROUTE: GID=0 type=2 called_party=[highlight #FCE94F]0650083[/highlight] sub= calling= calling_sub= dir=in complete=1 ses=0

[/pre]

 

[amriddle01]

The provider, CMLine RX means what's received on the line

13:41:08 245267349mS [highlight #FCE94F]CMLineRx[/highlight]: v=13
CMSetup
Line: type=Q931Line 13 Call: lid=13 id=11 in=1
Called[0650083] Type=National (2) Reason=CMDRdirect SndComp Calling[] Type=Unknown Plan=Default Pres=NAInterworking (2)
BC: CMTC=3K1Audio CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
BChan: slot=0 chan=2

 

[IPGuru]

Weird,
I have a vague idea I have seen this before but cant remember when or how I resolved it.

Is there anything silly set in the Prefix fields of the line?


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[janni78]

The Service Provider are sending Type=National so the IPO adds the national prefix from the Line.

Don't think they should send Called number as national but if you don't have a - in front of the numbers in ICR they should match anyway.

"Trying is the first step to failure..." - Homer

 

[daken]

That makes sence the number comming in as national.
just checked another system and calls are comming in as unknown.

have looged it as a fault with the provider so lets see how this pans out.

Have set the pri line as
prefix 9
National Prefix 90
internationla Prefix as 900

if i have the full number in the incommin call route it has no matches because of the leading 0 on the number

i take back it being a bug with that avaya software.


[pre]
ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=00AA(Remote)
Message Type = Setup
InformationElement = Sending Complete
InformationElement = BearerCapability
0000 04 03 90 90 a3 .....
InformationElement = CHI
0000 18 03 a1 83 81 .....
InformationElement = PI
0000 1e 02 84 83 ....
InformationElement = CallingPartyNumber
0000 6c 0c 21 80 37 38 34 35 34 31 37 37 30 33 l.!.xxxxxxx03
InformationElement = CalledPartyNumber
0000 70 07 81 33 35 36 35 30 30 p..[highlight #FCE94F]356500[/highlight]
16:09:33 2861092340mS ISDNL3Evt: v=5 stacknum=5 State, new=Present, old=NullState id=14
16:09:33 2861092341mS CMLineRx: v=5
CMSetup
Line: type=Q931Line 5 Call: lid=5 id=14 in=1
Called[[highlight #FCE94F]356500[/highlight]] [highlight #FCE94F]Type=Unknown[/highlight] (0) Reason=CMDRdirect SndComp Calling[90xxxxxx03] Type=National Plan=ISDN Pres=Allowed (0)
[/pre]

 

[janni78]

That's right, if you have a longer number in ICR for outgoing CLI the 0 messes up the best match logic.

"Trying is the first step to failure..." - Homer