search for: peering

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'. Correct? Apparently Asterisk doesn't

Hi to everybody my system is be attack, but I dont know what this means [May 27 15:12:24] WARNING[26018] chan_skinny.c: Partial data received, waiting (76 bytes read of 786) [chan_skinny.c] skinny_session[0][C-00000000] skinny_session: WARNING[May 27 15:52:32] Asterisk 13.8.0 built by root @ asterisk on a x86_64 running Linux on 2016-04-04 19:02:51 UTC [May 27 15:52:32] NOTICE[2306] cdr.c: CDR

This morning I did a rolling update from the latest 3.7.x to 3.12.4, with no client activity. "Rolling" as in, shut down the Gluster services on the first server, update, reboot, wait 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

Hello Guys I am facing a problem using cifs filesytem on centos 4.3 32 bit to connect to remote shares.we have DAS(Dell md1000) connected to a Dell 2950(win 2003 std).let me descibe the proc which i followed to access thi DAS via 2950.. 1) create a normal user account on Dell2950(win 2003) create 3 folders with names mysqhare1,myshare2,myshare3 in the storage area and assign all permissions to

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

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

I have three machines, all Ubuntu 12.04 running gluster 3.3.1. storage1 192.168.6.70 on 10G, 192.168.5.70 on 1G storage2 192.168.6.71 on 10G, 192.168.5.71 on 1G storage3 192.168.6.72 on 10G, 192.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

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. (24ms / 2000ms) [Mar 12 10:17:26]

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

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

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

Trixbox 2.2 Beta with freePBX 2.2.0rc1 I have a setup that looks something like this in ASCII art: Teliax IAX Trunk ------+ | V Embarq PRI ----> Tandem switch ----> Ottawa Office Server------+ +--------------> Lima Office Server -----+|

On Fri, 12 Jan 2018 at 01:34, Dj Merrill <gluster at deej.net> wrote: > This morning I did a rolling update from the latest 3.7.x to 3.12.4, > with no client activity. "Rolling" as in, shut down the Gluster > services on the first server, update, reboot, wait until up and running, > proceed to the next server. I anticipated that a 3.12 server might not > properly

You cannot do a rolling upgrade from 3.6.x to 3.10.x You will need downtime. Even 3.6 to 3.7 was not possible... see some references to it below: https://marc.info/?l=gluster-users&m=145136214452772&w=2 https://gluster.readthedocs.io/en/latest/release-notes/3.7.1/ # gluster volume set <volname> server.allow-insecure on Edit /etc/glusterfs/glusterd.vol to contain this line: option

Hi Diego, Just to clarify, so did you do an offline upgrade with an existing cluster (3.6.x => 3.10.x)? Thanks. On Fri, Aug 25, 2017 at 8:42 PM, Diego Remolina <dijuremo at gmail.com> wrote: > I was never able to go from 3.6.x to 3.7.x without downtime. Then > 3.7.x did not work well for me, so I stuck with 3.6.x until recently. > I went from 3.6.x to 3.10.x but downtime was

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_friend_req] 0-glusterd: Received probe from uuid:

>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

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

Hello List. Last month i started to face a strange issue on an asterisk server 1.8.9.3 built on Centos 5.3 x86_64 dedicated server. out of the blue UDP stops responding .. and keep getting the following output: ---------------------------------- Opening message for the problem -------------------------------------------------- [Mar 21 09:57:04] ERROR[6748] netsock2.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 documentation or