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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networked Magix unable to make outbound call

Status
Not open for further replies.

Delmar

Vendor
Oct 16, 2002
43
0
0
US
2 legends networked together.
Site A has just installed a PRI for outbound calls.
They want Site B to use this PRI for outbound calls.
Network has been up and running, both sides can call each other, transfer calls across with no problem.
Site A can make and receive outbound calls with no problem over the new PRI circuit.
Get fast busy when trying to make outbound call from Site B over Site A's PRI.

However if I route the calls over Site A's POTS lines then the calls will go through.

No Barrier codes required is programmed on both sites and they are set to unrestricted.

I think I have checked everything, but I may have missed something. Could it be a timing issue?
Any thoughts will be appreciated.
 
PRI INFORMATION



A Slot 6 Switch: MERLIN-Ntwk

A Slot 9 Switch: DMS-100

A System: By line

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 1 9 CallbyCall By Dial Plan

A Channel ID: 21 20 19 18 17 16 15 14 13 12
A 11 10 9 8 7 6 5 4 3 2
A 1

A Line PhoneNumber NumberToSend
A 841
A 842
A 843
A 844
A 845
A 846
A 847
A 848
A 849
A 850
A 851
A 852
A 853
A 854
A 855
A 856
A 857
A 858
A 859
A 860
A 861

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 80 6 ElecTandNtwk Route Directly to UDP

A Channel ID: 23 22 21 20 19 18 17 16 15 14
A 13 12 11 10 9 8 7 6 5 4
A 3 2 1

A Line PhoneNumber NumberToSend
A 817
A 818
A 819
A 820
A 821
A 822
A 823
A 824
A 825
A 826
A PRI INFORMATION


A 827
A 828
A 829
A 830
A 831
A 832
A 833
A 834
A 835
A 836
A 837
A 838
A 839

A Network Selection Table

A Entry Number: 0 1 2 3
A Pattern to Match: 101**** 10***

A Special Service Table

A Entry Number: 0 1 2 3 4 5 6 7
A Pattern to Match: 011 010 01 00 0 1
A Operator: none none none none none none none none
A Type of Number: I I I N N N N N
A Digits to Delete: 0 0 0 0 0 0 0 0

A Call-By-Call Service Table

A Entry Number: 0 1 2 3 4
A Pattern 0: 0
A Pattern 1: 1
A Pattern 2: 2
A Pattern 3: 3
A Pattern 4: 4
A Pattern 5: 5
A Pattern 6: 6
A Pattern 7: 7
A Pattern 8: 8
A Pattern 9: 9
A Call Type: BOTH BOTH BOTH BOTH BOTH
A NtwkServ: No Service
A DeleteDigits: 0 0 0 0 0

A Entry Number: 5 6 7 8 9
A Call Type: BOTH BOTH BOTH BOTH BOTH
A NtwkServ:
A DeleteDigits: 0 0 0 0 0

A Dial Plan Routing Table

A Entry Number: 0 1 2 3
A NtwkServ: Any service
A Expected Digits: 0 0 0 0
A Pattern to Match:
A PRI INFORMATION


A Digits to Delete: 0 0 0 0
A Digits to Add:

A Entry Number: 4 5 6 7
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:

A Entry Number: 8 9 10 11
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:

A Entry Number: 12 13 14 15
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:
 

A GENERAL OPTIONS ACCESS CODE: 889

A Barrier Code required for Non-TIE DISA lines: No
A Barrier Code required for TIE DISA lines : No
A Automatic Queuing enabled for DISA lines : No
A System Wide Barrier Code Length : 07
A Date and Time of Last Barrier Code Change : 01/13/00 03:26AM

A SYSTEM DEFAULT CLASS OF RESTRICTIONS (NON-TIE)

A Restriction : UNRESTRICTED
A ARS Restriction Level: 3
A Allowed Lists :
A Disallowed Lists :

A SYSTEM DEFAULT CLASS OF RESTRICTIONS (TIE)

A Restriction : UNRESTRICTED
A ARS Restriction Level: 3
A Allowed Lists :
A Disallowed Lists :
 
Just reviewing the info provided, one thing got my attention it looks like B Channel 22, line 862 is missing. If you have a full PRI ISDN, there will be 23 BCHs 1 DCH. The outgoing access problem may lie in the UDP & ARS programming and/or pool access, please post prints of that info so we can see what is there.

....JIM....
 
Thanks for the reply Jim,
Its only 21 channels, It is working now,
Turns out it was a clocking issue, Site a was set to Loop,
Site B was Loop also, I changed Site B to Local and it started working.
 
The ideal clocking would be to set site A to local and B to loop, because your mail clock source is the PRI. Since "Telco" is the most accurate source for this when using this type of configuration. You can check the Network Reference document for more detail, and/or the Feature Reference document.

Out of curiosity, what are channels 22 & 23 doing on the PRI?

....JIM....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top