Displaying 20 results from an estimated 800 matches similar to: "LAN sip-to-sip"
2015 Feb 20
2
sipsak 200 for a user, but 404 for a different user...why?
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 password 201
default No Yes
123
2015 Feb 16
1
SIP show peers: UNREACHABLE
I'm trying to configure SIP trunking. Now, I'm referencing "Asterisk
the definitive guide", 4th ed. While I don't have the page handy, I was
reading the suggestion to try SIP to SIP before proceeding to outside
connectivity. I'm aware that SIP trunking is a construct, but am,
obviously, learning the system.
What I'd like to do is from the CLI "ping"
2015 Feb 16
0
LAN sip-to-sip
It looks as if that is more of a question/issue with your router, rather than Asterisk.
I have SIP devices working on my LAN, all hardwired, and have no need to open any ports or have the router address SIP in any way
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
2015 Feb 20
2
sipsak 200 for a user, but 404 for a different user...why?
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:
thufir at doge:~$
thufir at doge:~$ sudo sipsak -vv -s sip:devries at
2015 Feb 20
0
sipsak 200 for a user, but 404 for a different user...why?
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 password 201
> default
2015 Feb 19
0
sipsak: 404 error
Hi,
I **think** that I have user of thufir101, because I get a 200 response
below, but I also get a 404. It seems to depend on how I send the ip
address/fqdn?
tleilax*CLI>
tleilax*CLI> sip show users
Username Secret Accountcode
Def.Context ACL Forcerport
201 password 201
default No Yes
2015 Mar 20
4
UNREACHABLE peer
I wasn't able to get much out of babytel, beyond the fact that I was,
apparently, sending options which is why I'm not getting 200 OK.
How can I, generally speaking, ping/telnet or otherwise test the
connection to get more data?
A connection to this peer directly from a softphone, Jitsi, works fine.
linux-k7qk*CLI>
linux-k7qk*CLI> sip show peer testcarrier
* Name :
2015 Feb 20
2
sipsak 200 for a user, but 404 for a different user...why?
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[3661] chan_sip.c: [Feb 20 15:13:19]
<--- SIP read from UDP:192.168.1.3:38154
2015 Feb 20
0
sipsak 200 for a user, but 404 for a different user...why?
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 enabled
> tleilax*CLI>
2015 Apr 08
2
dial out with channel variable; sub-string usage
I want to do something like:
exten => _NXXXNxxxxxx,1,Dial(${BABY}/${EXTEN})
exten => _Nxxxxxx,1,Dial(${BABY}/${EXTEN})
exten => _1NXXNxxxxxx,1,Dial(${BABY}/${EXTEN})
exten => _011.,1,Dial(Dial({TOLL}/${EXTEN})
exten => _9NXXXNxxxxxx,1,Dial(${BABY}/${EXTEN})
exten => _9Nxxxxxx,1,Dial(${BABY}/${EXTEN})
exten => _91NXXNxxxxxx,1,Dial(${BABY}/${EXTEN})
exten =>
2015 Feb 22
2
dialplan contexts syntax and terminology
I'm looking into the dialplan specifics:
tleilax:~ #
tleilax:~ # cat /etc/asterisk/extensions.conf
[general]
static=yes
writeprotect=no
[globals]
CONSOLE=Console/dsp ; Console interface for
demo
TRUNK=DAHDI/r1 ; Trunk interface
TRUNKX=DAHDI/r2 ; 2nd trunk interface
TRUNKIAX=IAX2/ASTtest1:test at 10.10.10.16:4569 ; IAX trunk
2015 Mar 23
0
trying to connect to asterisk with softphone (logs, etc)
In the Asterisk log I see:
---
[Mar 23 19:25:29] VERBOSE[4067] chan_sip.c: [Mar 23 19:25:29]
<--- SIP read from UDP:198.38.7.34:5065 --->
SIP/2.0 200 OK
To: <sip:16046289850 at sip.babytel.ca>;tag=sd3D4swKRc
From: <sip:16046289850 at sip.babytel.ca>;tag=as07c833c5
Via: SIP/2.0/UDP 96.48.217.39:5060;branch=z9hG4bK13c68eb7;rport
Call-ID:
2015 Feb 18
0
ports, routers and firewalls
I just want to make a SIP call from 192.168.1.3 to 192.168.1.4; or not
even a call. Ring? Beep? Ping? Some sort of "hello world" connection.
192.168.1.1 netgear router
192.168.1.2 asterisk (vicidial)
192.168.1.3 ubuntu client
192.168.1.4 mac OSX client (not shown)
Do I have a firewall problem which would impact a soft phone from
establishing a connection?
2015 Mar 20
0
UNREACHABLE peer
Turn on sip debugging for this peer and watch for the options sending
and response.
If you are getting a response to your options asterisk shouldn't be
marking the peer as unavailable.
is your asterisk behind a firewall?
On 20 March 2015 at 13:42, thufir <hawat.thufir at gmail.com> wrote:
> I wasn't able to get much out of babytel, beyond the fact that I was,
> apparently,
2015 Feb 21
0
connecting with Ekiga; diagnostic tools
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:
thufir at doge:~$
thufir at doge:~$ sudo sipsak -vv -s sip:thufir
2015 Apr 13
1
dial out with channel variable; sub-string usage
On 15-04-09 12:06 PM, Chad Wallace wrote:
>> but don't know where to put those lines. I have BABY defined as
>> >channel variable:
>> >
>> >BABY = SIP/babytel_out
>> >
>> >but that seems circular, somehow.
> You put them in the context for your clients... From what you show
> below, I'd say they go in the "local_200"
2015 Feb 20
0
sipsak 200 for a user, but 404 for a different user...why?
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 see:
>
> [Feb 20 15:13:19]
2004 Oct 06
1
Asterisk to BabyTel VoIP SIP Provider
Hi,
Does anyone has configured Asterisk to connect to BabyTel (a SIP
Provider in Canada) ?
Here is my sip.conf (I'm behind a firewall and I already opened
port 5060 and 5065 (udp and tcp) to my Asterisk server):
[general]
port = 5065
context = Test
insecure = very
register => 1514XXXXXXX:password@sip.babytel.ca
When starting Asterisk, the sip registration failed after 5
connecting
2015 Feb 22
0
dialplan contexts syntax and terminology
READ READ READ ....
http://www.asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/asterisk-DP-Basics.html
Regards,
Mitul Limbani,
Business Head,
Enterux Solutions Pvt. Ltd.
110 Reena Complex, Opp. Nathani Steel,
Vidyavihar (W), Mumbai - 400 086. India
http://www.enterux.com/
http://www.entvoice.com/
email: mitul at enterux.in
DID: +91-22-71967196
Cell: +91-9820332422
On Sun, Feb 22,
2015 Feb 22
0
101 called 102 success :)
I called 102 from 101 successfully! I have everything connected to my
home router. Asterisk is running on tleilax, so I used my Android phone
to call doge. Worked like a charm.
I'd been thinking that the firewall was blocking connections, but not at
all.
Anyhow, thanks to everyone who's help me out. I'm sure I'll have other
problems, but huge milestone.
-Thufir