asimm.it wrote:

ittel123 wrote:

Goodie wrote:
I am using IPPBX 2820 (f/w 3.5.4 RC5) and VigorPhone 350 (f/w 12202.26.1.03i)

It's quite frustrating as all missed calls show as 904 meaning I am unable to call the person back.

Any help would be greatly appreciated!

We're also suffering from that issue. It's not fixed in the newer firmware.

So it's either a provider issue (BT, Draytel etc) or a bug/feature that needs fixing or enabling.

We're also suffering with the same issue. I am currently in contact with BT and DrayTek on this as the ISDN Line we have with BT should have CLIP (it is an additional line feature which we ordered at the same time as the line). DrayTek have checked the logs of the IPPBX and say that the "Calling Party Number" is missing from the logs thus indicating that the feature is not present on the ISDN line.

I will post back once we have confirmation from BT that the feature is present and is working correctly on the line. If this happens then the ball is back in the DrayTek court so to speak.

Cheers!

Update

Apparently BT exchange engineers failed to activate CLIP on the ISDN line when the line was actioned. Have to wait until 01 March 2010 for an ISDN engineer to activate CLIP on the line at the exchange (apparently there is a shortage of ISDN engineers).

Will post back with another update and let you know the outcome.

If any one else is having a problem with CLIP it might be worthwhile raising a fault with your line provider so that they can test to see if it is actually enabled on the line!

Cheers guys. It might be that it wasn't switched on, even though it was asked for.

These are the logs:

28:15:38.760 ISDN2<----D Len = 8 LAPD NT C SAPI=63 TEI=127 UI P=0
Management Entity Identifier : 15
Reference number(Ri) : 0
Message type : identity check request
Action indicator(Ai) : 113

28:15:39.960 ISDN2<----D Len = 8 LAPD NT C SAPI=63 TEI=127 UI P=0
Management Entity Identifier : 15
Reference number(Ri) : 0
Message type : identity check request
Action indicator(Ai) : 113

28:17:08.960 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:19.160 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:19.160 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:29.360 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:29.360 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:39.560 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:39.560 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:49.760 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:49.760 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:59.960 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:17:59.960 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:10.200 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:10.200 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:20.400 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:20.400 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:30.600 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:30.600 ISDN2---->D Len = 4 LAPD TE R SAPI=0 TEI=115 RR P/F=1 NR=45
28:18:40.800 ISDN2<----D Len = 4 LAPD NT C SAPI=0 TEI=115 RR P/F=1 NR=45

Hi All,

Just an update.

Caller ID appears to be working on incoming ISDN calls since the lines CLIP feature was enabled at the exchange.

If anyone else has this issue please check with your lISDN ine provider 1st even if you made an order for CLIP doesn't mean that it will get activated at the engineer end of the order.

From my experience it is best to raise a fault with the ISDN line provider who should then be able to run a routine check to see if CLIP is functioning on the line.

All the best

Yup, our client's ISDN line had caller ID off for some reason too.

SIP caller ID works perfectly.