search for: sip_poke_noanswer

...E[3090]: chan_sip.c:12526 handle_response_peerpoke: Peer '17114-5' is now Reachable. (108ms / 2000ms) [Sep 12 22:11:05] NOTICE[3090]: chan_sip.c:12526 handle_response_peerpoke: Peer '17114-6' is now Reachable. (113ms / 2000ms) [Sep 12 22:12:08] NOTICE[3090]: chan_sip.c:15677 sip_poke_noanswer: Peer '17114-1' is now UNREACHABLE! Last qualify: 117 [Sep 12 22:12:08] NOTICE[3090]: chan_sip.c:15677 sip_poke_noanswer: Peer '17114-2' is now UNREACHABLE! Last qualify: 126 [Sep 12 22:12:09] NOTICE[3090]: chan_sip.c:15677 sip_poke_noanswer: Peer '17114-3' is now UN...

...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 'provider-13052181000' is now UNREACHABLE! Last qualify: 0 Dec 12 17:49:30 NOTICE[11565]: chan_sip.c:11564 sip_poke_noanswer: Peer 'provider-13052181001' is now UNREACHABLE! Last qualify: 0 Dec 12 17:49:30 NOTICE[11565]: chan_sip.c:11564 sip_poke_noanswer: Peer 'provider...

I've got a number (10) Cisco 7960's connected to my network. All the phones work perfectly except one. The asterisk console keeps throwing up: Jun 22 15:39:15 NOTICE[-1147470928]: chan_sip.c:5887 sip_poke_noanswer: Peer '4001' is now UNREACHABLE! Jun 22 15:39:27 NOTICE[-1147470928]: chan_sip.c:4925 handle_response: Peer '4001' is now REACHABLE! Jun 22 15:42:08 NOTICE[-1147470928]: chan_sip.c:4925 handle_response: Peer '4001' is now REACHABLE! Jun 22 15:43:12 NOTICE[-1147470928]: chan_...

...them back online, I loaded the dhcp-server onto another system (Also running Mandriva) and copied the dhcpd.conf to that pc. Now, after bringing that system online, the phones are bouncing up and down every few seconds with the following errors: [May 19 14:32:23] NOTICE[3231]: chan_sip.c:15778 sip_poke_noanswer: Peer '4231' is now UNREACHABLE! Last qualify: 39 [May 19 14:32:50] NOTICE[3231]: chan_sip.c:15778 sip_poke_noanswer: Peer '4276' is now UNREACHABLE! Last qualify: 40 [May 19 14:33:02] NOTICE[3231]: chan_sip.c:15778 sip_poke_noanswer: Peer '4247' is now UNREACHABLE! La...

...response: Peer '3201' is now REACHABLE! Sep 28 15:04:01 NOTICE[8182]: chan_sip.c:6678 handle_response: Peer '3289' is now TOO LAGGED! Sep 28 15:04:11 NOTICE[8182]: chan_sip.c:6672 handle_response: Peer '3289' is now REACHABLE! Sep 28 15:05:22 NOTICE[8182]: chan_sip.c:8059 sip_poke_noanswer: Peer '3201' is now UNREACHABLE! Sep 28 15:05:32 NOTICE[8182]: chan_sip.c:6672 handle_response: Peer '3201' is now REACHABLE! Sep 28 15:06:23 NOTICE[8182]: chan_sip.c:8059 sip_poke_noanswer: Peer '4881' is now UNREACHABLE! Sep 28 15:06:33 NOTICE[8182]: chan_sip.c:6672 han...

...r,verbose syslog.local0 => notice,warning,error,verbose But the logs look different: VERBOSE[7609][C-00000013] pbx.c: NOTICE[3042] chan_sip.c: Peer '1111' is now UNREACHABLE! vs. VERBOSE[7609][C-00000013]: pbx.c:2925 in pbx_extension_helper: NOTICE[3042]: chan_sip.c:30421 in sip_poke_noanswer: Peer '8884' is now UNREACHABLE! specifically, the messages coming from syslog have extra debugging information (which I am not interested in): pbx.c: chan_sip.c: vs . pbx.c:2925 in pbx_extension_helper: chan_sip.c:30421 in sip_poke_noanswer: Why are same log level settings pro...

...192.168.1.105 D N 5060 OK > (11 ms) Cached RT >=20 > I prune the realtime peers to no longer have gerrie002 in cache : >=20 > asterisk*CLI> sip prune realtime all > 3 peers pruned. > 2 users pruned. > [Mar 2 15:42:19] NOTICE[32498]: chan_sip.c:16612 sip_poke_noanswer: > Peer 'gerrie001' is now UNREACHABLE! Last qualify: 91 >=20 > The realtime peers are all gone : >=20 > asterisk*CLI> sip show peers > Name/username Host Dyn Nat ACL Port Status > Realtime >=20 > Internal call fails : >=20 >...

...ell that would mean I couldn't make phone calls because the Internet is down. Ryan [Jun 21 01:51:26] NOTICE[13657]: chan_sip.c:11569 sip_reg_timeout: -- Registration for 'xxxxxxx at newyork.voip.ms' timed out, trying again (Attempt #1) [Jun 21 01:51:46] NOTICE[13657]: chan_sip.c:22943 sip_poke_noanswer: Peer '1850' is now UNREACHABLE! Last qualify: 15 [Jun 21 01:51:46] NOTICE[13657]: chan_sip.c:11569 sip_reg_timeout: -- Registration for 'xxxxxxx at sip.flowroute.com' timed out, trying again (Attempt #1) [Jun 21 01:52:07] NOTICE[13657]: chan_sip.c:22943 sip_poke_noanswer: Peer ...

...y so far, and the rest still work in the current state. My logging looks like this with verbose turned up: [Jun 7 11:44:13] NOTICE[88483]: chan_sip.c:19842 handle_response_peerpoke: Peer '<user>' is now Reachable. (171ms / 2000ms) [Jun 7 11:46:17] NOTICE[88483]: chan_sip.c:25072 sip_poke_noanswer: Peer '<user>' is now UNREACHABLE! Last qualify: 203 [Jun 7 11:46:29] NOTICE[88483]: chan_sip.c:19842 handle_response_peerpoke: Peer '<user>' is now Reachable. (1888ms / 2000ms) When I call on this phone I get: [Jun 7 11:40:47] WARNING[88483]: chan_sip.c:3280 __si...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20040920/0629df7b/signature-0001.pgp

...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 '0049351111111' is now UNREACHABLE! Last qualify: 0 In the CLI I can see: Name/username Host Dyn Nat ACL Port Status 0049351111111/00493511111 192.168.200.11 D 5060 UNREACHABLE 0049351222222/00493512222 192.168.200.10 D...

...,verbose > > But the logs look different: > > VERBOSE[7609][C-00000013] pbx.c: > NOTICE[3042] chan_sip.c: Peer '1111' is now UNREACHABLE! > > vs. > > VERBOSE[7609][C-00000013]: pbx.c:2925 in pbx_extension_helper: > NOTICE[3042]: chan_sip.c:30421 in sip_poke_noanswer: Peer '8884' is > now UNREACHABLE! > > specifically, the messages coming from syslog have extra debugging > information (which I am not interested in): > > pbx.c: > chan_sip.c: > > vs . > > pbx.c:2925 in pbx_extension_helper: > chan_sip.c:3042...

I see repeated over and over the following messages: NOTICE[1142106560]: chan_sip.c:4988 handle_response: Peer '1001' is now REACHABLE then 5 minutes later: NOTICE[1142106560]: chan_sip.c:5958 sip_poke_noanswer: Peer '1001' is now UNREACHABLE both messages repeated over and over Any clue what I can do to fix this? Is there any where I can look up these Notices to find meaning? Thanks Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/p...

Hello list, Is there some parameter on sip.conf to always let the client reachable ? I'm trying to avoid .... this situation : Sep 3 09:49:29 NOTICE[135442432]: chan_sip.c:7653 sip_poke_noanswer: Peer '1264' is now UNREACHABLE! Sep 3 09:49:39 NOTICE[135442432]: chan_sip.c:6408 handle_response: Peer '1264' is now REACHABLE! Regards, -Jefferson Carvalho

...Jun 19 09:24:45 NOTICE[6632]: chan_sip.c:10029 handle_response_peerpoke: Peer '227' is now TOO LAGGED! (204ms / 200ms) Jun 19 09:24:55 NOTICE[6632]: chan_sip.c:10023 handle_response_peerpoke: Peer '227' is now REACHABLE! (148ms / 200ms) Jun 19 09:24:59 NOTICE[6632]: chan_sip.c:11777 sip_poke_noanswer: Peer '464' is now UNREACHABLE! Last qualify: 101 Jun 19 09:24:59 NOTICE[6632]: chan_sip.c:10029 handle_response_peerpoke: Peer '254' is now TOO LAGGED! (214ms / 200ms) -- Got SIP response 489 "Bad event" back from 192.168.3.10 Jun 19 09:25:09 NOTICE[6632]: chan_sip.c...

hello every body my connexion on ovh to pass in UNREACHABLE and not reidentified were not reboot the server. [Apr 7 20:17:21] NOTICE[19947]: chan_sip.c:15605 handle_response_peerpoke: Peer 'ovh' is now Lagged. (2067ms / 2000ms) [Apr 7 20:17:35] NOTICE[19947]: chan_sip.c:19829 sip_poke_noanswer: Peer 'ovh' is now UNREACHABLE! Last qualify: 2067 but my probleme is the adress ip 172.25.3.51 is not my adress. Really destroying SIP dialog '13ff06ae3e4bb3bf04987f5f5b497269 at 172.20.1.1' Method: OPTIONS Really destroying SIP dialog '6eac266b68dbc2566209fbb74aec76cb at...

[Mar 21 23:24:18] NOTICE[9931]: chan_sip.c:26242 sip_poke_noanswer: Peer '1000' is now UNREACHABLE! Last qualify: 110 [Mar 21 23:24:18] NOTICE[9931]: chan_sip.c:26242 sip_poke_noanswer: Peer 'patton' is now UNREACHABLE! Last qualify: 20 I also get errors for connections to SIP servers for which I have "register" entries in the [gene...

...However the Snom phones don't perform as well. I have played with qualify statement in sip.conf and at first I thought that I might have been OK with not using that argument, but it didn't work. I continue to get the following: *CLI> Feb 13 15:50:59 NOTICE[14043]: chan_sip.c:7971 sip_poke_noanswer: Peer '9093' is now UNREACHABLE! When this happens, I can't receive any calls (of course) but I can place outbound calls. Is this normal? Can anyone help me with this?

...erid="child2" <808> disallow=all allow=ulaw allow=alaw username=808 secret=xxxxx dtmfmode=rfc2833 host=dynamic mailbox=808 nat=yes qualify=yes canreinvite=no == Extension Changed 800[sip-phones] new state Idle for Notify User 812 [Oct 8 09:48:37] NOTICE[12030]: chan_sip.c:26141 sip_poke_noanswer: Peer '808' is now UNREACHABLE! Last qualify: 1 == Using SIP RTP CoS mark 5 - Executing [808 at sip-phones:1] Dial("SIP/815-000000d8", "SIP/808,20,t") in new stack [Oct 8 09:49:02] WARNING[12277]: app_dial.c:2218 dial_exec_full: Unable to create channel of type ...

Hello, I notice that Asterisk always sends Subscription-State: active, even when the SIP-peer is offline (IP-phone cut from power) : /[Jul 31 11:56:58] NOTICE[32273]: chan_sip.c:26194 sip_poke_noanswer: Peer 'testacc77000' is now UNREACHABLE! Last qualify: 49// //[Jul 31 11:56:58] Really destroying SIP dialog '78b0d1701d3694b1494a0c4b55344d57 at ip-sip-server:5060' Method: OPTIONS// //[Jul 31 11:56:58] set_destination: Parsing <sip:testacc77003 at 192.168.1.109:1024> for...