Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

ichabob (TechnicalUser)
27 May 04 22:15
Having problems dialing long distance after everything else works.  Got calls coming in on DID trunks getting my CNUM and CNAM. : )  

My first question though ... I can dial 9,NXX-5555 and call completes locally.  I dial ACOD,NXX-5555 and get a fast-busy.  I've turned on DCH messages to watch the difference in TON and digits dialed.  This is first hurtle.  I backed up database to make these changes.  I removed all RLI, DGT in 86.  I removed all SPN from 90 (all we used was SPNs).  The 9,NXX-5555 works as a NXX in 90.  Any feedback on this first issue?  I'm backing this database up, restoring old for now.  I will revert back to this database another evening to continue on with changes.  
johnpoole (Programmer)
28 May 04 7:47
could be several things, i normally make my new pri entr 0 in my rli, leaving everything else equal, i down the pri, bars steps over it using my old route. i know smaller switches might not be able to do that. Try deleting the 1 from you ld route, that would be my 1st guess. most ld carriers don't want to see it. you said 1-xxx-555-1212 was not going. did you try a not directory assist. ld. Spn bars is never a good idea. let me knowif i can help

john poole
bellsouth business
columbia,sc

hawks (IS/IT--Management)
28 May 04 10:38
You can not dial using the ACOD on a PRI. Did you build your LD as 1+ dialing?
johnpoole (Programmer)
28 May 04 11:36
i can dial using an acod on my pri, if you can't check tgar, targ. spn bars will make your switch much slower, i get a ring back outbound on the pri's before i can move my hand off the last number. with spn it works almost as fast as a cell phone.

john poole
bellsouth business
columbia,sc

hawks (IS/IT--Management)
28 May 04 11:47
Are we talking AC1 or RDB acod?
johnpoole (Programmer)
28 May 04 13:13
acod, my pri between my 81 and a 11, 4 digit acod, direct access without a problem.  

john poole
bellsouth business
columbia,sc

hawks (IS/IT--Management)
28 May 04 13:21
Have not tried it point to point just to the telco thanks for the info.
ichabob (TechnicalUser)
28 May 04 14:27
I had tried the RDB ACOD to the Telco.  So that is not a way for me to debug my BARS...?  Besides knowing what I'm doing, : )  ... what can I use to help get me through testing.  The SPNs was inherited and worked.  After we got the Telco switch to do NI2, name was working and local calls after changing to NXXs.  I had LDN0 blank originally, but had to enter an extension to get calls to come in.  Nothing would work for LD.  LD was 1+ and the telco accepts 1+.  I tried using NPA, NXX, SPNs using DMI's that added and deleted digits.  The message we are getting from the Telco for LD calls is, "you must dial a 1 or 0 ....".  Like I said, the telco is back the same and I restored our 11C to SPNs, and ifc d100 getting just calling number coming in.  Going to make another attempt this weekend maybe.
Reusser (Programmer)
28 May 04 19:40
1. You have to match protocals with whatever telco has at their end - You mentioned NI2 and then D100

2. What does the LD carrier say about these problems - are lines pic to them, what is you insert a 1010xxx number infront for you LD carrier or another carrier. You should work close with telco as they can look at the call setup and tell you what they need to see differently.

3. Since you are using SPN you may have to change the call type to NPA - use a DMI with now digit change just call type
ichabob (TechnicalUser)
29 May 04 18:25

1. Yes, it has been working using D100.  The telco doesn't support NI2, but is willing to test it in this case.  It is changed to NI2 when I test.

2.  Haven't spoke to the LD carrier yet.  Our BILLDN is setup of the trunk group at the telco and that is pic'd to our carrier.  We just dial 1+.

3.  I'll try it.  

Anyone familiar with debugging PRI messages on the Opt11?
vztech (Programmer)
1 Jun 04 21:20
Check your clid table some CO's may want to see correct info outpulsed NPA,NXX etc.Doesn't make sense that using ACOD doesn't work.

good luck
johnpoole (Programmer)
2 Jun 04 9:20
is this a ld pri that you are trying to dial local on? most ld pri's are ld ONLY.. if the ld carrier sees any number except a 0 or 1 as the leading, you'll get that recording. if your dialing a ld (1+nnn+nxx+4digits)..use your dmi to insert a 1...

john poole
bellsouth business
columbia,sc

ichabob (TechnicalUser)
2 Jun 04 22:36
I only have one PRI.  Local and LD must both go across it.  Using IFC d100, all were set to SPNs.  Digits dialed were digits sent to the local telco.  Now with IFC set to NI2, It appears that the Type of Number field and other programming is what might be incorrect.  I now have D-channels set to NI2.  Local numbers are NXXs and follow IFC route.  Long distance is set to SPNs and following a non ISDN route using A/B signalling.  I decided to not flip flop between d100 and NI2 for testing any longer, but I would like LD to follow the ISDN NI2 route eventually.  As for digits sent, when I turn on messaging for the D-channel, 1+NPA+NXX+XXXX is what is outpulsed, like before.  The difference is sending the TON field.  
johnpoole (Programmer)
3 Jun 04 8:41
try changing the dsel on your rdb, if that doesn't do it and the recording is saying you must dial a 1 or 0, insert a 1..

john poole
bellsouth business
columbia,sc

ichabob (TechnicalUser)
3 Jun 04 16:29
My d-channel messaging says that I'm sending 1+NPA+NXX+XXXX like before NI2.  The Telco did a DISPLAY CALL on the DMS and saw the digits mentioned.  They add 10288+ .... like before.  It seems to be something related to Billing DN which they still have setup or Numbering Plan or Type of Number, which are new parameters sent.  Still testing and confused.  Telco hasn't setup NI2 before either, so we could be lost.
ichabob (TechnicalUser)
3 Jun 04 18:04
A solution.  In table LTCALLS in the DMS-100.  Option BNS=SBN.  Special Billing number is used from table TRKGRP.  I'm not satisfied with how I understand the manipulation of NPA in AC1 and CTYP in DMI and how that sent different Type of Number and Number plan during the D-channel SETUP message, but I'm calling out with the DMS overriding the Billing Number.  

By the way ... I didn't want to admit it, but I'm the one in the CO and on the PBX trying the NI2.  I found the BNS option and added it along with TCAP_CNAM.  We've never offered it before.  We've only offered Calling Number using the SL1PROFL in the DMS on PRI not Calling Name.  It's handy using both sides sometimes, except when you run into something like this where I had no background in NI2 on either device.

ichabob (TechnicalUser)
3 Jun 04 18:04


Thanks for everyone's input.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close