similar to: asterisk 18.17.1 unreachable

Displaying 20 results from an estimated 20000 matches similar to: "asterisk 18.17.1 unreachable"

2018 Apr 12
3
Digium IP Phones UNREACHABLE after registration
I'm trying to solve a mystery for the last couple of days. I have a mix of D70, D50 and D40 behind NAT. Server is in a colocation, not a VPS. For several years, everything was working fine, no issues. A few days ago I started having problems at one particular site. NO CHANGES have been made to this office network - same router, switch and internet provider. No new equipment added or
2017 Apr 19
2
IAX2 getting stuck
On 4/19/17 4:09 PM, Antony Stone wrote: > On Wednesday 19 April 2017 at 22:54:51, Carlos Chavez wrote: > >> I have a server that had been operating for a few years now with >> IAX2 trunks to several other servers. Since yesterday all IAX2 trunks >> now say UNREACHABLE. > ...snip... > >> So far the only thing different is that the receive queue for port
2018 Sep 10
2
failed to find existing extension
On 2018-09-09 10:27, Antony Stone wrote: <snip > 1. Try removing one of the two commas. > > 2. Take a copy of your dialplan, and then strip out *everything* except > the > one context and the one number you want to match: > > [0705680837] > exten => 31705680837,1,NooP( Incoming 31705680837 on CC) > same => n,Answer(); > same =>
2004 May 23
1
IAX2 REACHABLE/UNREACHABLE
All, I have an issue with IAX that I can't comprehend. Approximately every eight minutes my servers go unreachable. They stay unreachable for exactly 10ms. I have two servers running IAX and it happens on both servers simultaneously. I have searched the archives and see similar issues, but not the exact same one. I am on the current CVS stable version of *. Also, during IAX calls,
2015 May 28
4
Peer is UNREACHABLE
Darryl Moore <darryl at moores.ca> schrieb: > I'd start by turning on sip debugging in asterisk > >sip set debug ip [your_phone_ip] Really destroying SIP dialog '490d1996593c8e11217828b71aae5c4d at 172.16.34.133' Method: OPTIONS Reliably Transmitting (no NAT) to 192.168.200.11:5060: OPTIONS sip:00493512222222 at 192.168.200.11:5060 SIP/2.0 Via: SIP/2.0/UDP
2017 Apr 19
2
IAX2 getting stuck
I have a server that had been operating for a few years now with IAX2 trunks to several other servers. Since yesterday all IAX2 trunks now say UNREACHABLE. No configuration changes have been made and no upgrades have been done. The server is running 11.16.0 (yes, we are planning upgrades but lets solve this first). The server has a USB ethernet adapter that got disconnected yesterday by
2005 May 27
3
Polycom phones, UNREACHABLE
I'm having some trouble with Polycom Soundpoint phones. I have had good luck deploying them on a local network, but now I've tried putting some in place which access their * server across the network. The * server is on a public IP and the polycoms are behind a NAT on a cable modem broadband connection. Every so often I get: May 27 16:12:08 NOTICE[29728]: Peer 'Polycom1' is now
2015 May 28
4
Peer is UNREACHABLE
Kevin Larsen <kevin.larsen at pioneerballoon.com> schrieb: > The phone you gave your wife is really old. Are you sure it supports SIP > OPTIONS? Can you make a call in or out to it? If you can, it is more > likely that it just doesn't support that and you can't use a qualify > statement. No, I'm not sure. And no, I can't make any call, right now... At least,
2015 May 28
4
Peer is UNREACHABLE
Hi list! I have a problem and I hope someone can help me... I configured an Asterisk on a VM to serve more accounts and act as a proxy to other SIP-providers. The first account running on my phone works without any problem. A second account, running on the phone of my wife, is always UNREACHABLE. I can just see in the log: [May 28 21:48:46] NOTICE[3646]: chan_sip.c:22933 sip_poke_noanswer: Peer
2006 Dec 07
0
sip qualify unreachable/reachable - ci$co 7940
I have logs full with this messages... I must have qualify turned on, because phone is behind firewall, main problem si, that phone is each hour about one hour unavailable! :'( I tried to modify minexpiry/maxexpiry sip.conf timeouts, but nothing help me. I'm using latest firmware 8.4 in phone, will be better to downgrade? to what version? (latest asterisk 1.4branch) [Dec 7 00:36:56]
2006 Dec 12
0
Disregistering Constantly - message: chan_sip.c:11564 sip_poke_noanswer: Peer 'provider-13052181000' is now UNREACHABLE! Last qualify: 0
Hi guys, I configure one Fedora Core Linux 5 for use with asterisk as gateway using Digium TE110P interconected in Alcantel 4100 I've set up it to register 100 voip numbers on my provider. All calls on Alcatel is send to asterisk. In some periods of day i receive this messages on asterisk console: Dec 12 17:49:30 NOTICE[11565]: chan_sip.c:11564 sip_poke_noanswer: Peer
2010 Aug 23
1
channel stay up when extension unreachable
Hi, We are using asterisk 1.4.34, ubuntu 10.4, below is suspicious activity recorded in our full log. Could you help us to explain what had happened. Thanks. === my friend, 801, from his room did a test by dialing echo test in freepbx, *43: [Aug 20 14:42:46] VERBOSE[14427] logger.c: -- Executing [*43 at from-internal:1] Answer("SIP/801-000003f5", "") in new stack [Aug 20
2015 May 28
3
Peer is UNREACHABLE
Darryl Moore <darryl at moores.ca> schrieb: > Ahh. Seen that before! That suggests to me that you don't have your > sip.conf records setup right. > > What's your sip.conf look like? Well, here what I wrote in my sip.conf: register => 00493511111111:MYSECRET at pbxluca/00493511111111 register => 00493512222222:MYSECRET at pbxfax/00493512222222 register =>
2010 Nov 13
1
Nat Issue - I think
Hi, I'm using qualify= on my asterisk server that provides outgoing pstn calls to a few companies. I've got one client in particular that has their own asterisk server which is connected to my server. This client seems to be having a nat issue. It's not a connectivity issue as i've tried constant pings and the line is up constantly. I'm getting the following: [2010-11-13
2011 Jun 07
1
tls/srtp: sip_xmit error: returned -2
I'm having trouble setting up tls/srtp secure communications on my Asterisk server- I'm still rather new at working with Asterisk. I have enabled tls and encryption and I have csipsimple with tls build on the phone. I'm currently only testing one phone with this capability so far, and the rest still work in the current state. My logging looks like this with verbose turned up:
2008 May 19
1
DHCP Failure screws up system
Maybe someone could point in the right direction. I have a small facility that's running around 40 Polycom 301/501 phones, Asterisk 1.4.18 running under Mandriva 2007.1. The phones were assigned a DHCP address in the 10.10.10.x range. Today, the DHCP server failed and to get them back online, I loaded the dhcp-server onto another system (Also running Mandriva) and copied the dhcpd.conf
2015 May 28
2
Peer is UNREACHABLE
Kevin Larsen <kevin.larsen at pioneerballoon.com> schrieb: > What kind of phone are we talking about, both yours that works and your > wife's that does not? Right! > Can you ping the unreachable phone and does it respond to a ping? I can ping both phones from the VM > Many phones will have a network test function built in to them to help you > determine if the phone
2018 Sep 08
3
failed to find existing extension
Hi all some how I'm getting confused: it seems I clobbered incoming calls from my sip provider. I can not imagine that my upgrade from 15.3 to 15.5 could be related I'm certain that dialling my own number, results in reaching asterisk, from my tcpdump. And on the asterisk console I get: pbx*CLI> == Using SIP RTP CoS mark 5 > 0x7f49ac54c040 -- Strict RTP learning after
2020 Oct 25
2
chan_sip doesn't authenticate on INVITE from a Dial() command
Hi. I'm trying to get Asterisk 13 to authenticate when it sends an INVITE, and for some reason it's simply not doing it. I've even resorted to reading the source code to try and work out what I'm doing wrong... In channels/chan_sip.c I find: * SIP Dial string syntax: * SIP/devicename * or SIP/username at domain (SIP uri) * or
2018 Sep 10
2
failed to find existing extension
On Monday 10 September 2018 at 21:54:33, Marcelo Terres wrote: > I have think it should be > > context=0705680837 > > Not > > context=[0705680837] Ha! You're right... so simple :) Antony. > On Mon, 10 Sep 2018, 20:43 , <asterisk at a-domani.nl> wrote: > > On 2018-09-09 10:27, Antony Stone wrote: > > > > <snip > > > > >