I have a BCM 400 4.0 and I am trying to set up a DISA DN and can't seem to get it working. I have a PRI. I set up Remote Package 01 to allow the proper Line Pools. I have added Pkg 01 to each line on the PRI. I add the 4 digit DISA DN DID to the Public Network page. When I dial the DISA number, I get a recording saying there are network difficulties(I don't think it is from the BCM) and not studder dial tone. If I put the DID in as a Target Line, it works fine. Does anyone have any thoughts on what I am missing. Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DISA over PRI not working
- Thread starter jlk53
- Start date
SupportDude
Technical User
Is your system set to Public Receive Length of 4?
You want to setup COS passwords, not remote packages, for use with DISA.
Check out page 458 of the Networking Configuration Guide.
-SD-
You want to setup COS passwords, not remote packages, for use with DISA.
Check out page 458 of the Networking Configuration Guide.
-SD-
- Thread starter
- #3
SupportDude
Technical User
Did you check out the documentation.
It speaks directly to doing DISA on a PRI in North America.
-SD-
It speaks directly to doing DISA on a PRI in North America.
-SD-
The reference to North America is only valid if your protocol is set for NI-2, DMS100 Custom, DMS250 or 4ESS Custom. If you're set to anything else, you don't get the options listed in the documentation (see page 178 of the 4.0 Networing Config Guide). It doesn't say how to set it up if you're set to NI-1 (or plain DMS100).
If anyone out there has gotten it to work with DMS100, please post the solution here as I'm trying to get it to work as well. No problem getting a set to ring (the DN that's set to the Public DISA DN in the Public Network settings). In my case, I have 4 digit DNIS with 3 digit DN's that don't match up, so how does it map the 4 digits coming down the PRI to the DISA DN? The only option you have is to assign the DN through the Target Line but all that does is ring the set.The call by call parameters don't even come up for DISA if you're set to DMS100.
If anyone out there has gotten it to work with DMS100, please post the solution here as I'm trying to get it to work as well. No problem getting a set to ring (the DN that's set to the Public DISA DN in the Public Network settings). In my case, I have 4 digit DNIS with 3 digit DN's that don't match up, so how does it map the 4 digits coming down the PRI to the DISA DN? The only option you have is to assign the DN through the Target Line but all that does is ring the set.The call by call parameters don't even come up for DISA if you're set to DMS100.
- Thread starter
- #7
SupportDude
Technical User
emilysdad ...
You don't have any other options to choose for protocol in North America.
Try this:
Assign digits to your DISA DN.
Go to Resources>Telephony Resources and highlight your PRI.
In the bottom panel select the Call by Call Service Selection.
Change the Translation Mode for Inwats (800)to By Number.
In the far right bottom pane click the Add button to add Digit Translations.
Configure the From field to match your received digits.
Configure the To field to match your DISA DN.
-SD-
You don't have any other options to choose for protocol in North America.
Try this:
Assign digits to your DISA DN.
Go to Resources>Telephony Resources and highlight your PRI.
In the bottom panel select the Call by Call Service Selection.
Change the Translation Mode for Inwats (800)to By Number.
In the far right bottom pane click the Add button to add Digit Translations.
Configure the From field to match your received digits.
Configure the To field to match your DISA DN.
-SD-
- Thread starter
- #9
SD, I tried what you suggested and I end up at the Attendant. Here is what I have:
Public and Private DISA DN 4001
Under Call by Call- Inwats/Translate(by number)/Digits to Translate(From 2125(DID sent down PRI) to 4001(DISA DN).
I have COS passwords programmed. Any thoughts as to why I get the Attendant instead of studder dial tone. Thanks
Public and Private DISA DN 4001
Under Call by Call- Inwats/Translate(by number)/Digits to Translate(From 2125(DID sent down PRI) to 4001(DISA DN).
I have COS passwords programmed. Any thoughts as to why I get the Attendant instead of studder dial tone. Thanks
I don't think it will work properly because if we are using the Inwats programming, wouldn't it only be invoked if the service provider sends the SID for that type service? In this case, the call is not coming into the PRI (mine anyway)as an inwats call and therefore the SID number would be different........I think. I'm not even sure NI-1 protocol sends those SID numbers.
Any network service guys know if this is the case?
Any network service guys know if this is the case?
SupportDude
Technical User
How many rings until you get the Attendant?
Is the Attendant the Prime Set for the PRI trunks?
In reading your result ... I had another thought. (and my apologies, I've not done this before either, just providing my interpretation of what I see in the docs and trying to help out. Always learning!)
What if we configured a target line with your recvd number of 2125. Leave the DISA DN at 4100. Don't assign the target line to any sets. Configure the "If Busy" field on the target line to prime and make the prime 4100.
I'm hoping for some spare time tomorrow to see if I can set this up in my lab. But, I rarely have spare time!
-SD-
Is the Attendant the Prime Set for the PRI trunks?
In reading your result ... I had another thought. (and my apologies, I've not done this before either, just providing my interpretation of what I see in the docs and trying to help out. Always learning!)
What if we configured a target line with your recvd number of 2125. Leave the DISA DN at 4100. Don't assign the target line to any sets. Configure the "If Busy" field on the target line to prime and make the prime 4100.
I'm hoping for some spare time tomorrow to see if I can set this up in my lab. But, I rarely have spare time!
-SD-
- Thread starter
- #12
Hi SD, thanks for all the effort. I tested it and it won't accept the DISA DN as a prime set.
In answer to your questions:
It goe to te attendant immediately.
Yes, the att is the prime set for the PRI.
Again, I really apprecite your hep with this.
In answer to your questions:
It goe to te attendant immediately.
Yes, the att is the prime set for the PRI.
Again, I really apprecite your hep with this.
SupportDude
Technical User
Bummer.
I've never configured call by call, so maybe emilysdad is correct about needing to see the service ID to invoke the feature.
It's going to the prime on the trunk because it doesn't know what else to do with the call. No matching Des code and no matching recvd number.
Eventually I'll test this out in the lab and see what I can come up with. There's always a way!![[shadeshappy]](/data/assets/smilies/shadeshappy.gif "[shadeshappy] [shadeshappy]")
Glad to help.
-SD-
I've never configured call by call, so maybe emilysdad is correct about needing to see the service ID to invoke the feature.
It's going to the prime on the trunk because it doesn't know what else to do with the call. No matching Des code and no matching recvd number.
Eventually I'll test this out in the lab and see what I can come up with. There's always a way!
Glad to help.
-SD-
SupportDude
Technical User
Tried this in my lab.
Every conceivable way I could think of, but none would work.
-SD-
Every conceivable way I could think of, but none would work.
-SD-
- Thread starter
- #17
Same here with a PRI the call just sets there then eventually times out. I can do it on an MICS with a PRI and it works perfect just like the book says. So I’m guessing somewhere in the BCM there’s another setting that needs to be turned ON or OFF.
- Thread starter
- #20
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question