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!

1+ numbers display "Disconnected" after dialing

Status
Not open for further replies.
Aug 11, 2006
54
US
When I dial out on a particular DID (Nsi8135551234), I get a busy tone and a DISCONNECTED message. When I hang up and press redial, it connects the call. If calling from the main number, this is not a problem.

I have an IPO406 v. 3.2(17)
 
sounds like a shortcode problem on the surface, but could be something wrong with your PRI signaling.

Did this just start happening all of a sudden?
 
Well first off everything was working fine. Then the carrier's PRI went down. So when they got it back up Long distance for that group was down and they said it was a PBX thing when I was getting "your service is temporarily disrupted..." So finally I got a guy to fix it and I tested it and it worked. As I'm trying to make my way out of the office, one of the employees said they could no longer make long distance again! I checked it and they could not dial 1+ out. However, when using the redial key, I'm able to dial out.
 
still sounds like a PRI or carrier issue. This doesn't happen to be a Time Warner circuit does it. Another poster on the forum here had something similar happen. Same weirdo stuff happening.

push back on the telco again.
 
FYI, depending on where your shortcode is that has that SI command in it, redial may not pick it up. Let me explain.

In order for me to have custom CLID, my users have a USER SC of 9/9Nsi5137773456. This works fine, but when redial is used, technically the user isn't "dialing 9", thus the SC is never hit and their "si" command in the shortcode isn't caught. That was a little while back, but it was an issue I experienced.

So, if your "si" command is being denied for some reason by the LEC, that may be why redial works. Try removing the "si" and the number following it and see if that works. If so, the bug in the switch actually helped you in this case, but I'd report to the LEC the CLID outbounding issue.

Hope this helps a bit...
 
I have the 'si' command under user restrictions. I haven't tried to do a redial to my cell to see what caller ID I get but what you're saying makes sense.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top