I have trixbox setup with two extentions and an outbound trunk (Vitelity). When I place a call it often takes 10-15 seconds to after dialing before getting a ring. This happens when I call another extension or an outside number. One of the extensions is on a Linksys PAP2 and it seems to take a little longer.
Long delay when placing call
After dialing the number, hit the # key (try on the pap2 first). Does the delay end?
Thats the dialing timeout, and is set on each device. The devices don't even send the number to asterisk until after it thinks your through dialing.
Thanks, that makes the pap work a little better on internal calls but I still get a delay dialing out. I noticed that this machine only has 256mb of ram. I think that may be part of the problem.
I don't know why but I had this problem and it resolved when I changed DNS servers in /etc/resolv/conf.
My original DNS entry was the router IP address, I changed this to my ISP's DNS servers and I had instant calling, after pressing the #
I'll give that a try. Thanks
I am having the same problem... What is the best way to edit that file? I tried using the config edit and it gives me this error...
------------------------------------------------------------------------------------------
Warning: copy(/etc/resolv.conf): failed to open stream: Permission denied in /var/www/html/maint/modules/09_configedit/cls_phpconfig.php on line 315
Write failed!
------------------------------------------------------------------------------------------
Log in to the system on the console or with putty.
I'm a MAC guy. In the console should I use nano to edit...?
I believe OSX has an ssh client built in. Go to a mac command line and type "ssh ip.of.your.trix.box" or, there is a mac version of putty available too.
Regardless, use whatever you're comfortable with to edit. I gather nano is all the rage with the new kids.
If you ever want to work with unix beyond your trixbox, it's in your best interest to learn to use vi -- vi is installed on everything and nano isn't.
You can even use the built in tutorial by typing "vimtutor". If that doesn't work, you probably don't have the vim-enhanced package installed, and you can install it by doing "yum install vim-enhanced" from the command line.
It can be very awkward at first, but you wouldn't believe what you can get done in a short time with vi that you just can't using a screen based editor.
Ok, vi pimping is over.
Interesting... Here is an error message I get when trying to log in with SSH.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
58:87:39:e1:fa:19:38:fe:92:0f:51:88:33:f6:ad:34.
Please contact your system administrator.
Add correct host key in /Users/James/.ssh/known_hosts to get rid of this message.
Offending key in /Users/James/.ssh/known_hosts:14
RSA host key for 192.168.1.110 has changed and you have requested strict checking.
Host key verification failed.
[Process exited - exit code 255]
I am not totally new to this... (honest). I don't get this error on another trixbox I have...
That error suggests that you've connected to that IP sometime before and that IP is now returning a different ID (upgrade perhaps or the same IP as another box in the past?)
The easiest thing is to edit the file on *your* machine /Users/James/.ssh/known_hosts. Use vi or nano or whatever text editor you prefer. Find the line(s) with the IP or hostname of trixbox and delete it. Now when you ssh to trixbox it will present a yes/no question since it thinks this is the first time. Say yes and you'll get in.
Offending key in /Users/James/.ssh/known_hosts:14
Delete line 14 of that file, then try again. Alternately, delete the whole /Users/James/.ssh/known_hosts file.
You ssh'd in to another machine with the same IP address, but a different fingerprint.
Dang! You guys are good! That is exactly what I did and it worked! The long delay is gone for now. Now our receptionists and agents will stop complaining... for a while anyway.
Member Since:
2008-03-18