search for: 8884

Hello, I am experiencing weird problem in Asterisk 16.2, possibly a bug. Same thing works fine in Asterisk 11. Here is the situation: I have 2 extensions on 2 phones. 4 extensions in total. phone 1: 8882 8382 phone 2: 8884 8384 And I have 2 SIP trunks for outgoing calls. I want to call via SIP1 when called via 8882 or 8884, and SIP2 when called via 8382 or 8384. And one last detail. SIP1 has caller ID spoofing enabled (used for call forwarding), so for outgoing calls, I have to explicitly set caller ID, otherwise...

...1183]: chan_iax2.c:9733 socket_process: Acking anyway localhost*CLI> [Sep 29 20:02:34] DEBUG[21184]: chan_iax2.c:10261 socket_process: Immediately destroying 3477, having received hangup localhost*CLI> [Sep 29 20:02:34] DEBUG[5752]: channel.c:1760 ast_hangup: Hanging up channel 'IAX2/8366-8884' [Sep 29 20:02:34] DEBUG[5752]: chan_iax2.c:4978 iax2_hangup: We're hanging up IAX2/8366-8884 now... -- Hungup 'IAX2/8366-8884' [Sep 29 20:02:34] DEBUG[5752]: app_dial.c:2315 dial_exec_full: Exiting with DIALSTATUS=CANCEL. [Sep 29 20:02:34] DEBUG[5752]: pbx.c:4306 __ast_pbx_run:...

...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 producing different...

...ile /home/bscott/Maildir/._NewMail-com/dovecot.index.cache: Corrupted virtual size for uid=234: 633278 != 633251 May 4 12:34:44 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/.Mailing Lists.Xorg Devel 2010-04/dovecot.index.cache: Corrupted virtual size for uid=312: 8884 != 8858 May 4 12:34:44 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/.Mailing Lists.Xorg Devel 2010-04/dovecot.index.cache: Corrupted virtual size for uid=312: 8884 != 8858 ... more of the same... May 4 13:02:54 f12barry dovecot: IMAP(bscott): Corrupted index cac...

...0 TASK: ffffffff80322b40 CPU: 0 COMMAND: "swapper" #0 [ffffffff80427ec0] schedule at ffffffff80294d9a #1 [ffffffff80427f98] cpu_idle at ffffffff8010b85d crash> kmem -i PAGES TOTAL PERCENTAGE TOTAL MEM 2621696 10 GB ---- FREE 8884 34.7 MB 0% of TOTAL MEM USED 2612812 10 GB 99% of TOTAL MEM SHARED 0 0 0% of TOTAL MEM BUFFERS 59585 232.8 MB 2% of TOTAL MEM CACHED 1325825 5.1 GB 50% of TOTAL MEM SLAB 358565 1.4 GB 13% of TOTAL MEM TOTAL HIGH...

...I stick to big names only (ATT, Sprint, etc.)? _____ <http://www.webunited.net/signature/webunited.jpg> 550 Fairway Drive Suite 210 Deerfield Beach, FL 33441 Online: www.webunited.net <http://www.webunited.net> Deon Rodden Toll Free: 1-877-538-5969 x 208 Phone: 954-418-8884 x 208 Fax: 954-418-8635 E-mail: drodden@webunited.net <mailto:drodden@webunited.net> _____ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040722/d5523381/attachment.htm

Short story: Would it be possible to get kernel-debuginfo-2.6.9-67.0.20.EL.x86_64.rpm on di.c.o? I have a need to run crash on a 2.6.9-67.0.20.ELxenU xm dump-core. Long story: Two Dell 6950 (now called R905, 4 Dual-Core AMD Opteron 8200 series) heartbeat/drbd nodes running the stock CentOS 5.2 Dom0. The domU's are the only resources in heartbeat. Dom1 is a perfectly running, updated, CentOS

...gs 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_no...

...Mlocked: 16 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 258708 kB LowFree: 87556 kB SwapTotal: 15624184 kB SwapFree: 15624184 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 20068 kB Mapped: 8884 kB Shmem: 168 kB Slab: 8324 kB SReclaimable: 3752 kB SUnreclaim: 4572 kB KernelStack: 1184 kB PageTables: 624 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 15753536 kB Committed_AS:...

Hi all Was curious how the beta is coming along. Was expecting to see it on monday, looking forward to playing over the holidays. Thanks, Jerry

....0%ni, 80.4%id, 14.3%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 8128776k total, 6991020k used, 1137756k free, 408756k buffers Swap: 8388604k total, 552356k used, 7836248k free, 185220k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10296 qemu 20 0 2366m 1.5g 8884 S 6.2 19.6 6:37.65 qemu-kvm 17334 qemu 20 0 2788m 1.7g 544 S 2.7 22.3 4576:25 qemu-kvm 9904 qemu 20 0 2358m 581m 8820 S 0.9 7.3 3:55.78 qemu-kvm 1 root 20 0 46880 8076 1372 S 0.0 0.1 0:27.00 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:10.4...

I'm trying (and failing) to install Icecast on a fresh-off-the-line Redhat 9.0 box. When I attempt to install the RPM with the command: # rpm -i icecast-2.0.1-1.i386.rpm ..the result is: error: Failed dependencies: curl >= 7.10.0 is needed by icecast-2.0.1-1 ...so okay, I wonder to myself, which verion of curl do I have running? # yum info curl ...and I learn that I am running a

...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_ex...

Funny current debian service files use a wrong PIDFile path (should be /var/run/amba/samba.pid). If I use Type=forking and an wrong PIDFile systemctl start samba must be CTRL-C'ed. Type=notify works with or without an proper PIDFile. Am 12.07.2016 um 22:47 schrieb Sonic: > On Tue, Jul 12, 2016 at 4:29 PM, Achim Gottinger <achim at ag-web.biz> wrote: >> Does your PIDFile

...f 0x00 (No unit mask) count 100000 samples % image name symbol name 347226 45.9445 ext3 (no symbols) 264664 35.0200 jbd (no symbols) 31778 4.2048 libc-2.5.so memset 10763 1.4241 xenstored main 8884 1.1755 libc-2.5.so _int_malloc 7053 0.9332 libc-2.5.so vfprintf 4264 0.5642 xenstored initialize_set So almost 80% of xenstored''s CPU time is attributed to ext3 & journalling modules, suggesting xenstored is doing alot of dis...

...8877 /usr/sbin/samba ├─8878 /usr/sbin/smbd -D --option=server role check:inhibit=yes --foreground ├─8879 /usr/sbin/samba ├─8880 /usr/sbin/samba ├─8881 /usr/sbin/samba ├─8882 /usr/sbin/samba ├─8883 /usr/sbin/samba ├─8884 /usr/sbin/samba ├─8885 /usr/sbin/samba ├─8886 /usr/sbin/samba ├─8887 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground ├─8888 /usr/sbin/samba ├─8889 /usr/sbin/samba ├─8892 /usr/sbin/smbd -D --option=ser...

...DC=example,DC=corp Replicate from faiserver.example.corp to location-000001.example.corp was successful. root at faiserver:~# samba-tool drs showrepl Default-First-Site-Name\FAISERVER DSA Options: 0x00000001 DSA object GUID: 5543435c-fccd-446a-bf71-777f4c6a3862 DSA invocationId: 20bce62d-cf4a-404a-8884-3552f409179d ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=example,DC=corp Default-First-Site-Name\LOCATION-000001 via RPC DSA object GUID: 2fbf25e8-acff-485b-8dea-2bc116869f5c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=exam...

...DC=example,DC=corp Replicate from faiserver.example.corp to location-000001.example.corp was successful. root at faiserver:~# samba-tool drs showrepl Default-First-Site-Name\FAISERVER DSA Options: 0x00000001 DSA object GUID: 5543435c-fccd-446a-bf71-777f4c6a3862 DSA invocationId: 20bce62d-cf4a-404a-8884-3552f409179d ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=example,DC=corp Default-First-Site-Name\LOCATION-000001 via RPC DSA object GUID: 2fbf25e8-acff-485b-8dea-2bc116869f5c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=e...

...DC=example,DC=corp Replicate from faiserver.example.corp to location-000001.example.corp was successful. root at faiserver:~# samba-tool drs showrepl Default-First-Site-Name\FAISERVER DSA Options: 0x00000001 DSA object GUID: 5543435c-fccd-446a-bf71-777f4c6a3862 DSA invocationId: 20bce62d-cf4a-404a-8884-3552f409179d ==== INBOUND NEIGHBORS ==== DC=ForestDnsZones,DC=example,DC=corp Default-First-Site-Name\LOCATION-000001 via RPC DSA object GUID: 2fbf25e8-acff-485b-8dea-2bc116869f5c Last attempt @ NTTIME(0) was successful 0 consecutive failure(s). Last success @ NTTIME(0) DC=DomainDnsZones,DC=e...

Hello everyone, I have setup two Samba AD DC's with BIND9_DLZ dns backend. faiserver.example.corp is one of them hosting all FSMO Roles. location-000001.example.corp is the second one. Both are in different subnets but can reach each other. Unfortunately replication only works from faiserver.example.corp -> location-000001.example.corp. In the other direction location-000001.example.corp