search for: peer

I'd love to understand what the function of the peer list returned by 'sip show peers' is for, especially when Realtime is used. If I start Asterisk with realtime enabled, a 'sip show peers' yields none. As each peer (phone) registers, or a call is made to the peer, Asterisk adds them to the list returned by 'sip show peers'...

...3] WARNING[2306] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 39. [May 27 15:52:33] WARNING[2306] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 47. [May 27 15:52:33] WARNING[2306] chan_sip.c: !!! PLEASE NOTE: Setting 'nat' for a peer/user that differs from the global setting can make [May 27 15:52:33] WARNING[2306] chan_sip.c: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users [May 27 15:52:33] WARNING[2306] chan_sip.c: !!! will be sent to a different port than replies for an exist...

...until up and running, proceed to the next server. I anticipated that a 3.12 server might not properly talk to a 3.7 server but since I had no client activity I was not overly concerned. All three servers are now updated to 3.12.4. The weirdness is that although the third server reports a proper peer status of "Peer in Cluster (Connected)" to both server 1 and 2, the first and second servers report to each other "Sent and Received peer request (Connected)" but show the proper "Peer in Cluster (Connected)" to the third server. [root at glusterfs1]# gluster peer st...

...end error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 CIFS VFS: Send error in Close = -9 TCP: Treason uncloaked! Peer 80.235.63.248:64721/37374 shrinks window 1814256320:1814257772. Repaired. TCP: Treason uncloaked! Peer 80.235.63.248:64721/37374 shrinks window 1814256320:1814257772. Repaired. TCP: Treason uncloaked! Peer 196.29.40.33:42283/80 shrinks window 1747071341:1747071342. Repaired. TCP: Treason uncloaked!...

Hi all, I'm currently in process of upgrading a replicated cluster (1 x 4) from 3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the first node, the said node fails to connect to other peers (as seen via 'gluster peer status'), but somehow other non-upgraded peers can still see the upgraded peer as connected. Writes to the Gluster volume via local mounts of non-upgraded peers are replicated to the upgraded peer, but I can't write via the upgraded peer as the local mount s...

Hi all, I tested with few Asterisk versions from 1.4.18 to 1.4.21, same result. Here is the problem: I have a peer -which is peer AND user- setted up like this [MyPeer] ; type=peer host=xxx.xxx.xxx.139 deny=0.0.0.0/0.0.0.0 permit=xxx.xxx.xxx.136/255.255.255.248 ;IP address from range 138 to 142 permit=yyy.yyy.yyy.yyy/255.255.255.255 context=from-MyPeer dtfmode=auto disallow=all allow=ulaw,alaw insecure=port,i...

...168.5.72 on 1G Each machine has two NICs, but on each host, /etc/hosts lists the 10G interface on all machines. storage1 and storage3 were taken away for hardware changes, which included swapping the boot disks. They had the O/S reinstalled. Somehow I have gotten into a state where "gluster peer status" is broken. [on storage1] # gluster peer status (Just hangs here until I press ^C) [on storage2] # gluster peer status Number of Peers: 2 Hostname: 192.168.6.70 Uuid: bf320f69-2713-4b57-9003-a721a8101bc6 State: Peer in Cluster (Connected) Hostname: storage3 Uuid:...

Hello list, I have nat=no and qualify=no in my sip peer definition and still my CLI is flooded with : [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (30ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable...

Hi, i attached logs. node3_cmd_history.log is empty because i did not run any command on node3. At logs i saw node 1 peer status contains ip addresses as peer. But other nodes node1 visible at it?s name . node 1 peer status is root at pri:/var/log/glusterfs# gluster peer status Number of Peers: 2 Hostname: 51.15.90.60 Uuid: eed0d6c6-90ef-4705-b3f9-0b028d769df3 State: Peer in Cluster (Connected) Hostname: 163.172....

Ready to scream here.. 1. After 6 months with Asterisk I'm STILL trying to understand the difference between a SIP user, friend and peer. 2. Exactly what resource does Asterisk use to send MWI to registered phones? I thought it was astdb? 3. It looks like it isn't astdb. It looks like it will only send MWI to a phone if it shows up in 'sip show peers'. 4. WHY then does a reload clear this list? Doesn't this list com...

I have 2610 XM with 1 Fastethernet and VIC2-2BRI. Dialin and dialout over pots is ok. Also inbound pots calls get redirected to Asterisk y.y.y.y So far so good. But I want to setup VOIP sessions with local carrier. I added dial-peer 40 for this. Session target x.x.x.x But calls will always get routed to the pstn peers 50 and 60. Peer x.x.x.x is never contacted or tried. My situation: PSTN -> CISCO -> ASTERISK OK ASTERISK -> CISCO -> PSTN OK ASTERISK -> CISCO -> VOIP NOT OK (only needs outbound calls)...

...was 0 and is now 9 -- Accepting AUTHENTICATED call from 10.149.32.11: > requested format = ilbc, > requested prefs = (ilbc|gsm), > actual format = ilbc, > host prefs = (ilbc|gsm), > priority = mine -- Executing Macro("IAX2/vmail-ottawa-peer-5", "vm|2502|DIRECTDIAL") in new stack -- Executing Macro("IAX2/vmail-ottawa-peer-5", "user-callerid|SKIPTTL") in new stack -- Executing GotoIf("IAX2/vmail-ottawa-peer-5", "0?report") in new stack -- Executing GotoIf("IAX2/vmai...

...roceed to the next server. I anticipated that a 3.12 server might not > properly talk to a 3.7 server but since I had no client activity I was > not overly concerned. > > All three servers are now updated to 3.12.4. The weirdness is that > although the third server reports a proper peer status of "Peer in > Cluster (Connected)" to both server 1 and 2, the first and second > servers report to each other "Sent and Received peer request > (Connected)" but show the proper "Peer in Cluster (Connected)" to the > third server. > > > [roo...

...25, 2017 at 7:46 AM, Yong Tseng <yongtw123 at gmail.com> wrote: > Hi all, > > I'm currently in process of upgrading a replicated cluster (1 x 4) from > 3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the first > node, the said node fails to connect to other peers (as seen via 'gluster > peer status'), but somehow other non-upgraded peers can still see the > upgraded peer as connected. > > Writes to the Gluster volume via local mounts of non-upgraded peers are > replicated to the upgraded peer, but I can't write via the upgraded p...

...l, > >> > > >> > I'm currently in process of upgrading a replicated cluster (1 x 4) > from > >> > 3.6.3 to 3.10.5. The nodes run CentOS 6. However after upgrading the > >> > first > >> > node, the said node fails to connect to other peers (as seen via > >> > 'gluster > >> > peer status'), but somehow other non-upgraded peers can still see the > >> > upgraded peer as connected. > >> > > >> > Writes to the Gluster volume via local mounts of non-upgraded peers > ar...

hi fellas, same old same in log of the probing peer I see: ... 2017-08-29 13:36:16.882196] I [MSGID: 106493] [glusterd-handler.c:3020:__glusterd_handle_probe_query] 0-glusterd: Responded to priv.xx.xx.priv.xx.xx.x, op_ret: 0, op_errno: 0, ret: 0 [2017-08-29 13:36:16.904961] I [MSGID: 106490] [glusterd-handler.c:2606:__glusterd_handle_incoming_fr...

>From glusterd.logs, It looks like address resolution issue in "glusterd_brickinfo_new_from_brick" functon call. After seeing command history, I could see that you have 3 nodes, and firstly you are peer probing 51.15.90.60 and 163.172.151.120 from 51.15.77.14 So here itself you have 3 node cluster, after all this you are going on node 2 and again peer probing 51.15.77.14. Ideally it should work, with above steps, but due to some address resolution volume create is getting failed, and from glust...

Hi all, we use OpenSER together with Asterisk. All SIP users registers with OpenSER and asterisk is doing the voicemail thing. We use the Asterisk RealtimeArchitecture for voicemail users and SIP peers. The database table for the sip peers is a view from the OpenSER subscriber table. The MWI for a user will only work, if the user object (sip peer) is loaded into memory and visible with the CLI command "sip show peers". This happens, for example, if the user call his own mailbox for ch...

......): Temporary failure in name resolution [Mar 21 09:57:04] WARNING[6748] acl.c: Unable to lookup 'pbx2.server.com' ----------------------------------------------------------------THEN ------------------------------------------------------------- [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'YYYY' is now UNREACHABLE! Last qualify: 10 [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'C1045' is now UNREACHABLE! Last qualify: 140 [Mar 21 09:57:04] NOTICE[6748] chan_sip.c: Peer 'XXXX' is now UNREACHABLE! Last qualify: 33 [Mar 21 09:57:15] NOTICE[6748] chan_sip.c:...

Hi everyone, I've been using gluster for a few month now, on a simple 2 peers replicated infrastructure, 22Tb each. One of the peers has been offline last week during 10 hours (raid resync after a disk crash), and while my gluster server was healing bricks, I could see some write errors on my gluster clients. I couldn't find a way to isolate my healing peer, in the...