What's the difference between user "123" and "devries"? Based on the
output here, they seem the same..?
tleilax*CLI>
tleilax*CLI> sip show users
Username Secret Accountcode
Def.Context ACL Forcerport
201password 201
Stefan Viljoen wrote:
Hi guys
I have some questions regarding the above
1. Why are there different options for timing?
Some systems don't have timerfd, some systems don't have DAHDI. The goal
is to have at least some sort of timing module for every system.
2. What are the differences bet
On 2/20/15 6:15 AM, thufir wrote:
What's the difference between user "123" and "devries"? Based on the
output here, they seem the same..?
tleilax*CLI>
tleilax*CLI> sip show users
Username Secret Accountcode
Def.Context ACL Forcerport
201
Le 18/02/2015 18:52, Eric Wieling a écrit :
I solved the issue by not answering the call as I assume others have done.
The only solution we found is to set faxdetect=no in the sip.conf of the
peer definition. The Set(FAXOPT(detect)=[yes|no]) command in the
dialplan is not taken in account.
On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote:
> A "sip set debug on" will give you more info on why you are getting the
> 404. It probably has to do something with your context/dialplan.
on tleilax:
tleilax*CLI>
tleilax*CLI> sip set debug on
SIP Debugging enabled
tleilax*CLI>
on doge:
Pardon, this might be off-topic. I'm reading:
http://en.wikipedia.org/wiki/Network_switch
For a setup of ~5 agents, would I be wrong in thinking that a generic 16
port unmanaged switch would fit the bill?
The first model to come up for me in an Amazon search is:
http://support.netgear.com/pro
Hi,
For a very basic setup it would work, but I would suggest POE at a
minimum, and vlan support if possible.
Gigabit uplinks, 10/100 for the poe ports
http://www.amazon.com/NETGEAR-ProSAFE-M4100-D10-POE-Ethernet-Managed/dp/B00AUEYX0Y/ref=sr_1_3?ie=UTF8&qid=1424462577&sr=8-3&keywords=netgear+
On 2/20/15 2:29 PM, thufir wrote:
On Fri, 20 Feb 2015 08:46:13 -0500, Andres wrote:
A "sip set debug on" will give you more info on why you are getting the
404. It probably has to do something with your context/dialplan.
on tleilax:
tleilax*CLI>
tleilax*CLI> sip set debug on
SIP Debugging
On Fri, 20 Feb 2015 15:07:35 -0500, Andres wrote:
> This is showing nothing so I don't think your test message even made it
> here. I think it looped in the 'doge' server.
I was wondering the same thing :)
in tleilax, I looked in /var/log/asterisk/messages and see:
[Feb 20 15:13:19] VERBOSE[
On 2/20/15 3:20 PM, thufir wrote:
On Fri, 20 Feb 2015 15:07:35 -0500, Andres wrote:
This is showing nothing so I don't think your test message even made it
here. I think it looped in the 'doge' server.
I was wondering the same thing :)
in tleilax, I looked in /var/log/asterisk/messages and
On Fri, 20 Feb 2015 17:11:53 -0500, Andres wrote:
> I don't think so. But you should also see the SIP messages on the
> console (sip set debug on) without having to look at the log file. Maybe
> something in your logger.conf is messed up.
that worked :)
tleilax*CLI>
tleilax*CLI>
[Feb 20 21:0
On Mon, 16 Feb 2015 16:12:04 -0500, John Novack wrote:
> My switch is not managed, and the router ports on the LAN side are all
> unmanaged, just a huge Ethernet "wirenut"
> You SHOULD be able to communicate between devices on the LAN without any
> firewall issue.
I think I might be doing this
I think I'm able to connect with Ekiga, at least it reports
"registered". Curiously, when I exit Ekiga and switch to SFLphone, it
isn't able to connect with the exact same parameters; it just says
"trying" and never resolves.
I'm not able to test outside connectivity because of too many hops:
13 matches
Mail list logo
