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!

PRI not providing Busy Tone for International calls

Status
Not open for further replies.

IGiveGreatDialTone

Technical User
Mar 23, 2005
36
0
0
US
Merlin Legend R7 PRI not providing Busy Tone for International calls only.

Calls made to a busy number in the US get a busy signal, calls made to a busy number OUTSIDE the US get dead air. This is an SBC(SNET) circuit configured as custom.

Any ideas?

***************************************************
Slot # 1: 408 GS/LS-MLX
Slot # 2: 408 GS/LS-MLX
Slot # 3: 400 GS/LS/TTR
Slot # 4: 408
Slot # 5: 408
Slot # 6: 408
Slot # 7: 408
Slot # 8: 012
Slot # 9: 408 GS/LS-MLX
Slot # 10: 008 MLX
Slot # 11: 100D

*****************************************************
DS1 SLOT ATTRIBUTES

Slot Type Format Supp Signal LineComp
11 PRI ESF B8ZS DMI-MOS 1

*****************************************************
PRI INFORMATION

Slot 11 Switch: 5ESS

System: By extension Base number: 2039852500

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

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

Line PhoneNumber NumberToSend
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855

Network Selection Table

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

Special Service Table

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

Call-By-Call Service Table

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

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

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service Any service Any service Any service
Expected Digits: 0 0 0 0
Pattern to Match: 0
Digits to Delete: 0 7 0 0
Digits to Add:

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

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

Entry Number: 12 13 14 15
NtwkServ: Any service Any service Any service Any service
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:
 
I suppose we can assume calls made to Overseas numbers that are not busy RING, is that correct?

So, where does that point the trouble to?

Just looking at the setup as posted, I see no reason why calls that Go through work ok and Busy ones do not.

What does SBC say about this problem?
 
merlinman:

Yes, overseas calls ring correctly and complete with no problem.

SBC says it may have to do with the "name" format I am sending with the setup message.
 
Well, I am rather certain you have no control over that. All the Legend/Magix provides is some CANNED translations under the SWITCH TYPE.

I have seen nothing in the translations that allows any changes to anything called name format.

Perhaps they can give more details.

Have they ever had any other LEGEND Clients with this issue?

 
Usually with isdn/ss7 signalling, call progress tones are provided by the far-end, but certain disconnect types (busy, not in service, trouble) are provided by the 'local' CO. In your case, that could be the SNET co, or the Legend itself. I'd say it's in SNET's translations, since they're the ones that would decide if/how to send the 'busy' signalling message back to you, once they've gotten it from the foreign destination. Have you explored changing to the other PRI profile?

I agree with MM, you can't control name. In the US, callerID name is 'retrieved' from the far end, not sent forward, so even if SNET is getting it, they should be ignoring it. That's what they do in all their other locations.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top