Asterisk/FreePBX not connecting internal calls

Running the software on RHEL5, have to since this a government server. Followed this guide to the ‘T’, http://www.powerpbx.org/content/centos-asterisk-freepbx-install-guide-centos-v5x-asterisk-v16x-freepbx-v26x except for obviously no using Cent OS. Everything seems to be running fine when I open up the Web GUI, created all of the extensions, am using Twisted Pair’s WAVE Dispatch for soft phones. They register properly, I am able to talk to the Asterisk server, and am able to get the time when I hit *60 and any other feature codes.

When I dial from the soft phone to another extension though I get, “I’m sorry, that number is not valid”.

It’s not the soft phone software, as they work properly with TrixBox.

Any thoughts? Thanks

Chris

BTW

Running:
FreePBX 2.6.0
Asterisk 1.6.0.17
RedHat Enterprise 5 64bit

Any resolution to this? My server is doing the same thing too.

Chris (LowFire)-

Two item’s - If you send SIP and debuf log output we can assist with the issue. Do any other SIP devices work?

Second Issue - I have a business relationship with Twisted Pair that I would rather not discuss in an open forum. If you don’t mind please send me your contact information in a PM I would like to chat with you about your dispatch integration and some things we have going on with Twisted Pair.

Regards…

Chris,

Have a simular setup with Telex consoles… Bet it’s a route pattern, or a bad context assignment. Hard to tell without the CLI log… You can get this from the console or from /var/log/asterisk/full.

Also you can run a trace within Asterisk or fire up wireshark to look at what’s happening.


[Dec 14 07:57:54] NOTICE[4314] chan_sip.c: Peer ‘1110’ is now Reachable. (1ms / 2000ms)
[Dec 14 07:57:54] NOTICE[4314] chan_sip.c: Peer ‘1111’ is now Reachable. (1ms / 2000ms)
[Dec 14 07:58:06] NOTICE[4314] chan_sip.c: Peer ‘1112’ is now Reachable. (1ms / 2000ms)
[Dec 14 07:58:06] NOTICE[4314] chan_sip.c: Peer ‘1113’ is now Reachable. (1ms / 2000ms)
[Dec 14 07:58:27] WARNING[4400] res_agi.c: unable to send SIGHUP to AGI process 4401: No such process
[Dec 14 07:58:27] WARNING[4400] res_agi.c: unable to send SIGHUP to AGI process 4402: No such process

Guess that explains why it won’t connect, I will have to search around to find out what the AGI process is

[Dec 14 07:59:40] NOTICE[4314] chan_sip.c: Registration from ‘“9*” sip:9*@10.75.1.6’ failed for ‘10.75.1.2’ - No matching peer found

And that would explain why my trunk is not connecting. Probably a setting wrong in my Cisco 2811

Thanks for getting me pointed in the right direction, quite the learning curve on this :slight_smile:

SkykingOH – PM coming your way

Chris