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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Explain TGAR & TARG 3
- Thread starter pronei
- Start date
Try these links. You'll find information that may help answer your questions.
Regards,
Harry
"The legitimate powers of government extend to such acts only as are injurious to others. But it does me no injury for my neighbour to say there are twenty gods, or no god. It neither picks my pocket nor breaks my leg." --Thomas Jefferson
Regards,
Harry
"The legitimate powers of government extend to such acts only as are injurious to others. But it does me no injury for my neighbour to say there are twenty gods, or no god. It neither picks my pocket nor breaks my leg." --Thomas Jefferson
-
1
- Thread starter
- #3
I am asking because I am trying to test several routes I have built by dialing the acod then a direct number.
On my CS1000E v5. I dial the ACOD for route 2, I get dialtone again, I enter the phone number I want to call. After a couple seconds, I get Fast Busy with Release & Try Again on the set and ERR404 on the PBX.
ERR0404
No default tree exists.
What is No Default Tree?
On my CS1000E v5. I dial the ACOD for route 2, I get dialtone again, I enter the phone number I want to call. After a couple seconds, I get Fast Busy with Release & Try Again on the set and ERR404 on the PBX.
ERR0404
No default tree exists.
What is No Default Tree?
-
1
- #4
It sounds like an entry related to Code Restriction or NFCR or Digit Conversion in the route data block is missing or refers to a NFCR/FCR/DCNO that does not exist.
I'd start by looking at the DCNO entry in the Route Data Block and trying to match it up with a LD49 IDC table.
Either way, "tree" in the context of your error, is going to relate back to something in LD49
GHTROUT.com | FAQs | Recent Replies
I'd start by looking at the DCNO entry in the Route Data Block and trying to match it up with a LD49 IDC table.
Either way, "tree" in the context of your error, is going to relate back to something in LD49
GHTROUT.com | FAQs | Recent Replies
911guru
Programmer
- Nov 10, 2007
- 437
And just to throw in my 2 cents worth.
Remember TARG/TGAR/NCOS/FRL and TENANT service are all ignored when you have ESA configured correctly.
911Guru
E911 FAQs are located at:
Remember TARG/TGAR/NCOS/FRL and TENANT service are all ignored when you have ESA configured correctly.
911Guru
E911 FAQs are located at:
- Thread starter
- #6
pronei: as far as I know your statement is true. But the error is an odd one, and "tree" can be applied to more than NFCR, so I would turn every stone.
NFCR - New Flexible Code Restriction applies to outgoing, and that's also done in LD49. "Code Restriction Tree" is a common term to speak about NFCR. I'll bet these will lead you to the problem.
-There is an FCR_DATA gateway in the Customer Data Block
-At the FRL prompt in the Route Data Block, there is a reference to FRL-NFCR (FRL xx xx)
-In LD49, REQ PRT TYPE FCR will lead you to the config of FCR trees
GHTROUT.com | FAQs | Recent Replies
NFCR - New Flexible Code Restriction applies to outgoing, and that's also done in LD49. "Code Restriction Tree" is a common term to speak about NFCR. I'll bet these will lead you to the problem.
-There is an FCR_DATA gateway in the Customer Data Block
-At the FRL prompt in the Route Data Block, there is a reference to FRL-NFCR (FRL xx xx)
-In LD49, REQ PRT TYPE FCR will lead you to the config of FCR trees
GHTROUT.com | FAQs | Recent Replies
-
1
- Thread starter
- #8
GHTROUT,
Thank you. Following those steps led me to the fix. I don't understand how it fixed the problem, but it did. I know absolutely nothing about FCR.
I had to add a CRNO entry in LD 49. There were none programmed, so I copied the only FCR entry my other CS1000M 4.5 switch had and added:
Now I can make test calls using ACOD + phoneNum
Thank you. Following those steps led me to the fix. I don't understand how it fixed the problem, but it did. I know absolutely nothing about FCR.
I had to add a CRNO entry in LD 49. There were none programmed, so I copied the only FCR entry my other CS1000M 4.5 switch had and added:
Code:
REQ prt
TYPE fcr
CUST 0
CRNO 0
CRNO 0
INIT ALOWNow I can make test calls using ACOD + phoneNum
- Status