- Silver, 250 points or more
I´ve setup my first SPA9000 @ a customer. I´m having some difficulties though. Some times it´s not possible to dial outbound. According to the ITSP they see that the user try to dial out, but the call is disconnect from the SPA side. Any idea where to start troubleshooting??? According to a colleage of mine the company transfers large files over the DSL line. The SIP trunk is configured with QoS on rtp ports 30000-30030 towards the ITSP.
Please help me :)
I don't see anything of much use in the syslog message. It's best to have the syslog server running when the SPA9000 boots and then supply the entire log file.
How do you know that the ITSP is not receiving the SIP REGISTER requests?
2009-05-28 12:20:04 Local3.Debug 192.168.10.2 RegFail. Retry in 30
I see that this wasn't the first registration attempt
2009-05-28 12:20:34 Local2.Debug 192.168.10.2 RSE:GetServerAddrErr(ITSP,2)=-101
This could be a clue.
Did you sanitize the log information? The following in red does not look correct:
"[email protected]>;tag=488b62d4a6bb100bo2<013><010>To: "" [email protected]><013><010>Call-ID: [email protected]<013><010>CSeq: 23080 REGISTER<013><010>Max-Forwards: 70<013><010>Contact: "" [email protected] IP:5060>"
Check that the:
- SPA9000 is attempting to register with appropriate credentials based on what the ITSP provided
- Router has working DNS server IP addresses configured
- Router has next-hop / default gateway configured [can a PC on the LAN ping www.google.com for examle?]
- SPA9000 INTERNET port is being used and that nothing is connected to the SPA9000's ETHERNET port
- SPA9000 has correct Gateway, NetMask, and DNS server IP addresses
The https://www.myciscocommunity.com/docs/DOC-3032 describes logging and has a link to the syslog utility provided by Cisco [login required]
You can use any free syslog server available on the Internet if you prefer.
Congratulations on your installation. The next one will be easier. :-)
If bandwidth is an issue, the call quality usually deteriorates and becomes choppy [jitter] but calls are seldom dropped for this reason.
Large downloads will not affect the SPA9000 Voice System, provided you followed the QoS steps etc. in the Installation Guide: https://www.myciscocommunity.com/docs/DOC-1749 starting on page 40
Be sure to verify that the main switch has QoS enabled. Verify that there is no upstream switch which may not have QoS properly configured.
You didn't mention the size of the installation. How many phones, SPA400s, PSTN lines, ITSP lines? Is auto attendant being used? Is SPA400 voicemail deployed? How many concurrent calls, AA, and vmail sessions when calls are dropped?
Are there any hung calls? SPA9000 web-ui > PBX status
Suggestions on troubleshooting this:
Look for patterns, when do calls get dropped, specific days of week, specific time of day, specific work load, etc.
Enable debug on the SPA9000 and check the logs for clues
Run Wireshark on the network between the SPA9000 and the ITSP where drops are experienced, check the traces for anomalies when call drops are reported.