Morning Asterikians, I've just got my nice shiny quadBRI card, and it seems to be working very well - except for one little issue - CallerID. The card is currently connected to an ISDN2e line in P2P mode, and an S0 adapter on our existing alcatel PBX. The S0 connection recieves callerID and displays it correctly - the 2e line doesn't, and BT have said that CLID was enabled on the line two days ago. Does anyone have any pointers on this? My configuration is avaliable on request. Thanks, Jon
> I've just got my nice shiny quadBRI card, and it seems to be working > very well - except for one little issue - CallerID. > > The card is currently connected to an ISDN2e line in P2P mode, and an S0 > adapter on our existing alcatel PBX. The S0 connection recieves callerID > and displays it correctly - the 2e line doesn't, and BT have said that > CLID was enabled on the line two days ago. Does anyone have any pointers > on this?Just a quick check, is it connected to 'real' ISDN2e or a Business Highway ISDN port? If the later, make sure that BT have turned caller display on the ISDN port and not on one of the analogue ports - this is a common mistake they make when taking your order. Linus
Which brand of card did you get? Sincerely, Stephen Karrington Dreamtime.net Inc. http://www.dreamtime.net http://www.emailblaster.us Corporate Office 101 California Street, 22nd Floor San Francisco, CA 94111-5802 Voice - 877-203-9308 Fax - 310-943-2606 Dreamtime is your global choice for worldwide communication services, viral marketing software and direct sales channel automation. ===8<==============Original message text==============Morning Asterikians, I've just got my nice shiny quadBRI card, and it seems to be working very well - except for one little issue - CallerID. The card is currently connected to an ISDN2e line in P2P mode, and an S0 adapter on our existing alcatel PBX. The S0 connection recieves callerID and displays it correctly - the 2e line doesn't, and BT have said that CLID was enabled on the line two days ago. Does anyone have any pointers on this? My configuration is avaliable on request. Thanks, Jon _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ===8<===========End of original message text===========
On Wed, Apr 07, 2004 at 12:37:43PM +0100, Jon Fautley wrote:> Morning Asterikians, > > I've just got my nice shiny quadBRI card, and it seems to be working > very well - except for one little issue - CallerID. > > The card is currently connected to an ISDN2e line in P2P mode, and an S0 > adapter on our existing alcatel PBX.Is this an omnipcx?> The S0 connection recieves callerID > and displays it correctly - the 2e line doesn't, and BT have said that > CLID was enabled on the line two days ago. Does anyone have any pointers > on this?I assume the callerid is also being displayed on the alcatel handsets? or is this just callerid generated on internal calls? If it is then that should show the bt line is setup correctly. I have callerid working from a bt 2e line in ptp mode using zaphfc. So assuming the bri-stuff versions match the only difference would be the quadbri card. Not sure where that leads because I think/thought all the callerid stuff would be handled by libpri from a q.931 SETUP message on the d-channel and not be driver/card specific. I could only get my s0 box to operate in ptmp mode, so there would be change in the signalling line in zapata.conf, but then if you weren't changing that nothing tends to work rather than just callerid. I also note that you have to match the msn assigned to the s0 when dialling out through the omnipcx whereas bt doesn't seem to be as fussy, but again nothing todo with callerid.
Hi Pedro, please do a "bri debug span X" on the span with the BRI line. Look at the SETUP message, the incoming caller ID is in the "Calling Party IE". If you do not see the caller ID in that IE then your telco is not providing incoming caller ID on your line, some telcos like to charge extra for such basic isdn features. -- best regards Klaus -- Klaus-Peter Junghanns CEO, CTO Junghanns.NET GmbH Breite Stra?e 13 - 12167 Berlin - Germany fon: (de) +49 30 79705390 fon: (uk) +44 870 1244692 fax: (de) +49 30 79705391 iaxtel: 1-700-157-8753 http://www.Junghanns.NET/asterisk/ Am Mi, 2004-05-19 um 15.26 schrieb Pedro Vela:> Hi, > > I have a Junghanns.net quadBRI PCI Card with Telefonica ISDN BRI line, and > we have in zapata.conf usecallerid=yes > and hidecallerid=no, but we have not the caller ID. > > Can I make some configuration to solve this? > > Thanks, > > Pedro > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users