Problem Presenting Numbers

[FocusTechnology]

Hi All,

We have a customer who has an IPO V8.1 with ISDN30 using "Type 5" Number Presentation via BT.
They want to send out a specific DDI when a user dials which we can do and know works from other systems using .sXXXXXXX etc.
The problem is that for some reason we cannot present anything through this ISDN30 trunk other than the main bearer numbers.
We have tried .w .sXXXXXX etc at all level including in ARS, the main short codes, under user short codes etc.
The traces show that the number IS being presented to the ISDN30 and this IS a valid DDI on the ISDN30 line.

ISDN Layer3 Pcol=08(Q931) Reflen=2 ref=0065(Remote)
Message Type = Setup
InformationElement = BearerCapability
0000 04 03 80 90 a3 .....
InformationElement = CallingPartyNumber
0000 6c 08 00 80 32 37 36 32 37 36 l...276276
InformationElement = CalledPartyNumber
0000 70 0c 80 30 37 35 39 30 38 34 39 36 30 39 p..xxxxxxxxxx (masked my mobile number but it shows correctly)
InformationElement = Sending Complete

Can anyone shed any light on this or has anyone else run into this and is there a fix? OR are we actually doing something wrong?

The other odd thing is that apparently a dialler they have can present ANY number it wishes including numbers that are NOT DDI's including mobile phone numbers which everything I have read about BT presentation suggests isn't possible!!

 

[RTGDFM]

I have had this a few times recently where BT have forgot to turn it on when they have built the circuit.

The dialler wouldn't be able to send out any number on ISDN unless its a DDI number on that circuit. OFCOM wont allow it. However you can on SIP as long as you own the number.

ACSS SMEC
APSS SMEC
ACA IP Telephoney Implement

 

[FocusTechnology]

Hi RTGDFM, BT swear blind that it is enabled on the circuit.
They also say that the number is a valid DDI and we can confirm that by dialling in to it which works fine and routes through the IPO, its just the outgoing that's the problem.
They don't have SIP.

 

[amriddle01]

The system sends the number out to BT, that's all it can do. If BT don't present it from that point there is nothing the IP Office can do it's their issue, as much as they protest to the contrary only they can fix it.

I assume you are matching the number of digits they send you? i.e if they send 6 for DDIs you may need to send 123456 as oppose to 01234 123456, as depending on age/type of exchange they can be fussy about this

 

[RTGDFM]

Have you tried putting a TREND on the kit to check its presenting it. If you can prove it with a trend they cannot argue. Ask to speak to the ISDN guys when you log a fault as all the other people do is run a line test which wouldn't show anything up.

As amriddle says if the system is sending it out that's all the Kit can do.

BT would swear blind there is no fault even if the cable had been cut into a building (actually had this happen).



ACSS SMEC
APSS SMEC
ACA IP Telephoney Implement

 

[amriddle01]

Indeed, I've also had ISDN2 line checks come back as passing when I am stood in front of them and the lights are off and pairs disconnected, being line powered how can that pass?

 

[IPGuru]

send the full tel no including STD code
the best short code to use is probably something along the lines of:-

sc:?
tn: .si<full 11 digits of number to send>
feature dial

if this does not work have a quick check on sys mon to ensure the number is indeed being sent then pass the issue back to BT
this would not be the 1st time they have been mistaken

BTW you do not leave level 5 peresentation to send a CLI for a valid DDI, level 5 presentation is to enable you to send numbers that are not registered to the circuit (for example passing on inbound CLI )


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

 

[IPGuru]

I have had BT say an analog line is fine whilst i have been holding the bare pares in my hand
"If you cant detect that as a fault then you clearly have something wrong, come & fix it "

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

 

[FocusTechnology]

Hi IPGURU Thank You!!

On ALL our other systems a simple .sxxxxxxx works but not in this case.
By using .sixxxxxxxx it did work so its something to do with the ISDN provider.
This has solved my issue and the presentation of the numbers now appears to work.

Is the .s, .si, .w shortcode format an industry standard (never looked at them on another system) that the line provider uses to take info from the outbound call, I just don't understand why this one would be different to any other we have used.

Thanks!