Hi Snowman, You're quite correct, the service main number is usually automatically presented as the main OLI. However, in the past I've asked BT to change this to one of the DDI numbers which they did. The trouble with that is that (as Firebird correctly pointed out) BT isn't the account...
Oh, I forgot to say.... the ISDN30 is using 8 channels with a common or garden variety number which is far from memorable. The (non BT) service provider has provided the customer with a geographical 'cloud' number (not a DDI range as such). This number is ported to the ISDN30 headline number...
I've got a problem with a BCM50 fitted with PRI ISDn30 only ringing extension 221 (via target line 125). Ring group 001 has all of my extensions in it and has all the target lines allocated but not trunks 65-72 (I suspect this is correct). What's the correct procedure here for setting up...
I need to present a full 11 digit STD DDI number as the main outgoing ident for all og calls on my PRI equipped BCM50. I tried changing the public network received number length to 10 and then entering the number (minus the leading 0) as the OLI but this didn't seem to work. I noticed that...
I need to present a full 11 digit STD DDI number as the main outgoing ident for all og calls on my PRI equipped BCM50. I tried changing the public network received number length to 10 and then entering the number (minus the leading 0) as the OLI but this didn't seem to work. I noticed that...
I've got a problem with a BCM50 fitted with PRI ISDn30 only ringing extension 221 (via target line 125). Ring group 001 has all of my extensions in it and has all the target lines allocated but not trunks 65-72 (I suspect this is correct). What's the correct procedure here for setting up...
Hi Guys, I'm probably missing something really silly but I've got a newly provisioned ISDN30 PRI circuit connected to my DTM-PRI MBM in expansion chassis 1 (on a BCM50 r3) and I can't get dial tone (9). It's properly configured in Telephony Resources as DTM-PRI, enabled and the correct 8...
Thanks for the info. Unfortunately, the system had been well and truly locked down by the previous maintainer so no joy there. In the end we had to resort to defaulting the system and reprogramming (with the able assistance of another company with the correct kit). All working OK now and the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.