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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can't make/receive external calls
- Thread starter mandg
- Start date
- Thread starter
- #3
You'll have to forgive me- I've been thrown to the wolves here. I didn't set this up and have no training on it.
So, I'm going to guess that by "PSTN ACCESS/GATEWAYS" you're talking about the WAN device- in which case it's a Cisco 7200.
How can I check if they're registered with the Callmanager? I'm presuming through the CallManager Administration??
The response I get in both cases (in/out) is a busy signal.
So, I'm going to guess that by "PSTN ACCESS/GATEWAYS" you're talking about the WAN device- in which case it's a Cisco 7200.
How can I check if they're registered with the Callmanager? I'm presuming through the CallManager Administration??
The response I get in both cases (in/out) is a busy signal.
yep the 7200 is prob your gateway to the PSTN cloud-
is the ciruit(s) you have connected to the gateway a T1? Check and see you have a green link light on whatever port the voice circuit connects to-
check in the CM admin page (choose: device/gateway) that the 7200 is registered with an IP address
see if you find anything
is the ciruit(s) you have connected to the gateway a T1? Check and see you have a green link light on whatever port the voice circuit connects to-
check in the CM admin page (choose: device/gateway) that the 7200 is registered with an IP address
see if you find anything
jneiberger
Technical User
The best thing to do would be to call Cisco TAC and have them walk you through all the troubleshooting steps on the phone.
jneiberger
Technical User
Why not? That's why you pay for support. If your users are being affected and you can't figure it out on your own, which makes more sense: 1) Open a case with TAC, or 2) Ask about the situation on a forum in hopes that perhaps someone may have some idea of what's happening.
I have no problem with people doing both 1 and 2, it's actually a good idea to check in multiple places for help, but TAC is far more able to help with these sorts of problems when you're in a hurry.
I have no problem with people doing both 1 and 2, it's actually a good idea to check in multiple places for help, but TAC is far more able to help with these sorts of problems when you're in a hurry.
- Thread starter
- #8
OK, here's the update. I did go ahead an look at the things MG2005 suggested and they both seemed pretty kosher. But as jneiberger pointed out I was in a bit of a rush and so opened a case with Cisco. I was origainlly relucatant since our Smartnet support expired and I knew the call would cost $400. Reagrdless, I made it and we got it fixed.
Turned out that I had a bad T1 port on the 7200. MCI verifed that the circuit was good and the Cisco rep informed me that the 'slow busy' signal was not being generated by the CallManager, so it must be the router. The fix was to swing the T1 port over to another port on the card and hope that it would work and I didn't have to RMA another card. It did work and I can only assume that the storms we had the evening before somehow fried the port :-(
Thanks for your help regardless. The lesson learned here is that this company needs to send me to training or continue spendoing $400 a pop for these calls.
Turned out that I had a bad T1 port on the 7200. MCI verifed that the circuit was good and the Cisco rep informed me that the 'slow busy' signal was not being generated by the CallManager, so it must be the router. The fix was to swing the T1 port over to another port on the card and hope that it would work and I didn't have to RMA another card. It did work and I can only assume that the storms we had the evening before somehow fried the port :-(
Thanks for your help regardless. The lesson learned here is that this company needs to send me to training or continue spendoing $400 a pop for these calls.
i dont prefer option 1 or 2. Both should be last resort.
If you're administering any type of phone service or any system in general, you should have basic understanding of trouble isolation. Is the circuit down or up, is there connectivity between circuit and system, etc. the more you know before calling TAC the better.
they support Cisco equipment not your circuits
also, not everyone purchases maintenance contracts or support!! =)
If you're administering any type of phone service or any system in general, you should have basic understanding of trouble isolation. Is the circuit down or up, is there connectivity between circuit and system, etc. the more you know before calling TAC the better.
they support Cisco equipment not your circuits
also, not everyone purchases maintenance contracts or support!! =)
jneiberger
Technical User
Point well taken. We prefer to be self-maintained, as well, but there's no way I'd buy a system like this and not have maintenance on it, at least until I and my other team members could be truly called Cisco IPT experts. Until that time, TAC will be on my speed dial. LOLoh i couldnt do it all alone, im surely no "IPT expert". I have TAC support for advanced troubleshhoting or when im stuck an dneed direction, but i always try and do my own research/due dillegence before involving them when necessary.
I still say they are a superb resource (as well as the CCO login on ciscos site) but basic troubleshooting skills in house are still needed, and will only help you fix a trouble faster and more efficiently.
I know in this persons case he is new to the system hes administering, and i could never understand how a company could "throw someone to the wolves" on a business critical system without basic training but i see it does happen! So he really should try and do it himself with people like us assisting and he'll never forget what hes learned. If his company cared so much about downtime they wouldnt have throen him into a system or technology he hasnt experienced yet. Not like im telling him to install or upgrade rteh system himself lol, just giving him basics to look for when he has no phone service. I would also have told him to call TAC if the issue seemed more severe
I still say they are a superb resource (as well as the CCO login on ciscos site) but basic troubleshooting skills in house are still needed, and will only help you fix a trouble faster and more efficiently.
I know in this persons case he is new to the system hes administering, and i could never understand how a company could "throw someone to the wolves" on a business critical system without basic training but i see it does happen! So he really should try and do it himself with people like us assisting and he'll never forget what hes learned. If his company cared so much about downtime they wouldnt have throen him into a system or technology he hasnt experienced yet. Not like im telling him to install or upgrade rteh system himself lol, just giving him basics to look for when he has no phone service. I would also have told him to call TAC if the issue seemed more severe
- Status
Similar threads
- Locked
- Question
