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!

Cannot dial main btn from internal extensions

Status
Not open for further replies.

cknipe

MIS
Jul 28, 2005
597
US
Hi we have a 3300 Cx that is running 4.0 sp1 and we recently switched carriers and ported a few of our old published numbers into our new service. I have built and auto attendant and pointed the number we ported at the AA via a speedcall. Whats odd is out of all the ported numbers I cant dial the main line from internal sets. It just so happens that I am outpulsing the main line as our caller ID as well. I have a hunch that this has something to do with the issue because when I got comcast on the line to look at it, the said they are seeing cause code 17 *user busy on their end. But internal users has no issues dialing the 4 digit speedcall extension either. I took a ccs trace of the call to the BTN 713-774-6671 and then the call to the 2nd number 713-774-6672. I was hoping someone can makes sense of these traces below.

16:44:32 RI2 DPN 2 CRM/CIM ;30;
16:44:38 RO2 DPN 21 ISRM_I ;10;*1#*50*6212#*100*D.Speer#*19*Z#
16:44:38 RO2 DPN 22 SSRM_I *58*CW*XaXq@@@@HLIhYp#*58*C6*001#
16:44:38 RO2 DPN 26 SSRM_C *58*CL*E*0*6212*C0000841*A#7137746671
16:44:38 RI2 DPN 7 NIM *51*3#
16:44:38 RI2 DPN 17 CRM/CIM ;8;*166*1 2 3 4#*234*DP#
16:44:46 RO2 DPN 21 ISRM_I ;10;*1#*50*6212#*100*D.Speer#*19*Z#
16:44:46 RO2 DPN 22 SSRM_I *58*CW*XaXq@@@@HLIiC`#*58*C6*001#
16:44:46 RO2 DPN 26 SSRM_C *58*CL*E*0*6212*C0003461*A#7137746672
16:44:46 RI2 DPN 7 NIM *51*3#
16:44:46 RI6 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*100*7137746671 7137#
16:44:46 RI6 DPN 22 SSRM_C *233*`IBb#*58*CI*W4#*50*6671#6672
16:44:47 RO6 DPN 16 NSIM ;1C;*100*Embedded Voice#
16:44:47 RO6 DPN 1A NAM *1*1 3#*50*6000#*166*4 6#
16:44:47 RI2 DPN F NIM *4*4#*240*`X`#
16:44:47 RI2 DPN 13 NAM *4*4#*166*1 2 3 4#
16:44:47 RI2 DPN A CCM *58*CP*G#
16:44:48 RO6 DPN 9 NSIM ;1C;*100*;7F;#
16:44:48 RO6 DPN 1A CCM *1*1 3#*50*6013#*166*4 6#
16:44:48 RI2 DPN A CCM *58*CP*G#
16:44:55 RO2 DPN 2 CRM/CIM ;30;
16:44:55 RI2 DPN 2 CRM/CIM ;30;
 
This is my first stab at it:

16:44:46 RI6 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*100*7137746671 7137#

This suggest to me that you need to absorb 6 digits on your incoming PRI in the trunk attributes form. It's looks to me to be reading the 1st 4 digits instead of the last 4 digits of the incoming number.

Dry Aquaman

 
Thanks for the idea. The issue is still occuring but I have a work around that worked fine for me. I think I mentioned above that 6671 and 6672 both point to my auto attendant. since 6672 worked fine all along when dialed from inside, I just edited the ars for 7137746671 to use a digit modification to replace the whole number on the way out to 7137746672. The customer doesnt know whats going on all they know is that it works now.
 
Am I correct in assuming that dialing 7137746671 from an outside number works fine?

If so, then I would agree that the Telco is blocking the call for reasons unknown.

May I also ask why it is necessary for you to be able to make this call (other than testing)

**********************************************
What's most important is that you realise ... There is no spoon.
 
kwb...youre third question is exactly why im ok with leaving this as a work around and not spending 5-10 hours chasing and calling back the telco if I dont have to. There really wasnt a good reason why they needed it working just that it is annoying and makes them feel like something is wrong. You are correct in that 6671 works from all outside callers without issue...only internal sets have issues dialing this. I remember seeing this at other sites in one example, we save this company lots of money by switching from at&t to a no name carrier. All these sites would have old pbx's connected to an old local analog lines or pri's. The no name carrier was connected to a pri card that was installed on a 3300 in a colo in a central location. as we started to port at&t's numbers into no name carriers PRI, I always found that no name carrier would pre provision their PRI and we would not be able to dial numbers that were to be ported in the next 48 hours. It was kinda like they were jumping the gun which messed up outbound dialing on the 3300. That is the closest scenario that I have seen that is similar to this. sorry it is so long winded.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top