change trunk group x", remove all members referencing the card.
"remove sig x", remove the signally channel (if it was a PRI, unlikely on a G3siV5, since PRI only came out in V6 I beleive)
That should do it, then you can of course do a "remove ds1 01AXX", and totally remove it, once it is not being referenced on any signalling or trunk group form.
You might also have to do a "change synch", and pick a different synchronization source, if that DS1 was being used for that (temporarily, you can put it back later)
You are correct, it's wasn't a PRI, the system doesn't support it. Learned that the hard way, it's from an old T1 we had in here.
I'm in the midst of moving over to a new service provider, and I want to test to make sure the circuit is good. So I'm going to bring up the T1 on our old DS1 board that's still in.
A concern I have now having seen your directions, when/if I go to change the signal on the current live board (the one we actively use), will I lose the DID programming? If so, where would I find that?
You won't have a signalling group, if you don't have a PRI.
(do a "list sig" to check)
The DID's are just 3 or 4 digit (or 5 digits in some cases) extension #'s, they are most likely arriving via in-band signalling on the existing T1 (touchtones from the T1 vendor)
If you remove the channels from the T1, yes, you will lose inbound/outbound calls from that T1, just while they are removed.
You may come out better buying a DS1 pack form the secondary market and installing it for the new circuit. This will let you test everything before making it live. When you get it up and are confident that it is working fine cut to it. Then remove the translations from the old board and you will have a spare. Not a bad pack to keep around Just in case.
"A people that values its privileges above its principles soon loses both."
- Dwight D. Eisenhower (1890-1969), Inaugural Address, January 20, 1953
For the best response to a question, read faq690-6594
That's pretty much what I'm doing. I have 2 DS1 cards in the system. Currently only one is being used. The other is programmed for an old tie to another facility that no longer exists, it hasn't been plugged into anything in years.
It's actually causing the occasional synch error because the system still tries to use it as a synch source.
Heh...almost sounds like I know what I'm talking about. I really need to take an Avaya course.
You can just use that unused pack, once you remove the old trunk group and programming, reprogram it for your new provider, you can even add in a few channels into your existing T1 trunk group for testing, and once its working, put in the rest of the members, then remove the current working members from the trunk group... sounds like you have what you need to do this, without bringing down or affecting your current T1 provider
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.