Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 954
  • Last Modified:

Incoming calls not working with Asterisk 1.4.9

Background:
AsteriskNOW is set up on a server. The entire network (including phones) is connected to the firewall and then to a Bell router. The entire system was working flawlessly with an old number, but incoming calls stopped working when the main number was ported over to a new number.
Situation:
Outgoing calls are normal and working. Internal extension-to-extension calls work fine. Incoming calls are not connecting to Asterisk. The ISP says that Asterisk is returning a 404 error.

I'll post config files and CLI output if necessary.
0
alexatsearidge
Asked:
alexatsearidge
  • 3
  • 2
1 Solution
 
jfaubiontxCommented:
Sounds like you need to update the inbound routes. The system probably had a route specifically for the old number and no default route.
0
 
feptiasCommented:
Can you capture a SIP trace for an inbound call and post it back here. To enable SIP logging at the CLI, use the command:
sip set debug

To switch it off again, the command is
sip set debug off

You probably need to configure an inbound route or DID that matches the incoming number. However, to see the exact format being used by the new provider, it would be simplest to capture the SIP packets and inspect them.
0
 
alexatsearidgeAuthor Commented:
This just in:
It works now, but I didn't touch anything. It just magically works. It's happened before where it randomly starts working again and then stops working.

Any ideas?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
jfaubiontxCommented:
Maybe the provider wasn't sending the right number of digits. You might look back through the /var/log/asterisk/full log file to see what the provider was sending before and after the calls started working.
0
 
alexatsearidgeAuthor Commented:
The situation seems to have resolved itself. The "full log" file is missing. Thanks for everyone's help.
0
 
alexatsearidgeAuthor Commented:
Problem is no longer relevant. No solution provided. Case closed.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now