search for: 0100000000

...iated as g729 on all four streams. Nuance with this call is that it's from a WebRTC client which doesn't transmit any audio, could this be influencing Asterisk? Is this a known scenario, something obvious or should I be logging something in JIRA? In the below +27888888888 (chan_sip) calls 0100000000 (chan_iax), negotiates g729 on both legs of the bridged call, exclusively receives g729 media from 0100000000 (chan_iax) but then transmits g711a media to +27888888888 (chan_sip). Herewith the scrubbed logging with SIP debug: [2020-09-19 23:42:19] VERBOSE[2637] chan_sip.c: <--- SIP read from UD...

...Asterisk? I couldn't post the asterisk debug in the mailing list, perhaps we could consider increasing maximum messages sizes from 40 KiB in 2020? I subsequently opened a case in JIRA instead (https://issues.asterisk.org/jira/browse/ASTERISK-29096). In the below +27888888888 (chan_sip) calls 0100000000 (chan_iax), negotiates g729 on both legs of the bridged call, exclusively receives g729 media from 0100000000 (chan_iax) but then transmits g711a media to +27888888888 (chan_sip). Herewith the scrubbed and reduced dialogues, full details are available in the JIRA case: [2020-09-19 23:42:19] VERBOS...

Hi, We have a scenario where inbound calls from an upstream provider (chan_sip) sent downstream (chan_iax2) negotiates only g729 yet RTP media contains g711. Both the upstream and downstream trunks are limited to only offering g729 whilst the initial invite from our upstream provider offers both g711 and g729. Asterisk presumably simply forwards the media from iax2 trunk encapsulation to sip

...Asterisk? I couldn't post the asterisk debug in the mailing list, perhaps we could consider increasing maximum messages sizes from 40 KiB in 2020? I subsequently opened a case in JIRA instead (https://issues.asterisk.org/jira/browse/ASTERISK-29096). In the below +27888888888 (chan_sip) calls 0100000000 (chan_iax), negotiates g729 on both legs of the bridged call, exclusively receives g729 media from 0100000000 (chan_iax) but then transmits g711a media to +27888888888 (chan_sip). Herewith the scrubbed and reduced dialogues, full details are available in the JIRA case: [2020-09-19 23:42:19] VERBOS...

...in my Asterisk? I have to setup in dongle.conf ? Or in extensions.conf? And the code for recive I found this site http://asterisk-service.com/page/chan-dongle-use I have to To save Subscriber Number before? See the error log in my Asterisk pbx.c:6796 __ast_pbx_run: Channel 'Dongle/dongle1-0100000000' sent to invalid extension but no invalid handler: context,exten,priority=URA,+5511965380290,1,Noop(),1 Thanks in advanced.

...bit OT. I'm using VoiceTrading for some calls -premium route- and can't get CID to work despite the fact that CALLERID(num) and CALLERID(name) are setted. I ask in VT->myAccount to accept calls from my IP without checking username & secret. On incoming calls the CID is setted to 0100000000 If I accept calls from username & secret and no IP relation, CID is always different and not related to something I know, doesn't matter which country is called. I read in some forums that setting secret=secret:username and username=CID should work. I tried, doesn't work. Anyway it...

Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some information here but none was helpfull to me. Anyone? I have 4GB memory and a AMD Turion II X2 M500 (

Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen

...00000000ddfb0000 (usable) BIOS-e820: 00000000ddfb0000 - 00000000ddfbe000 (ACPI data) BIOS-e820: 00000000ddfbe000 - 00000000ddfe0000 (ACPI NVS) BIOS-e820: 00000000ddfe0000 - 00000000ddfee000 (reserved) BIOS-e820: 00000000ddff0000 - 00000000de000000 (reserved) BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000120000000 (usable) NX (Execute Disable) protection: active DMI present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) e820 update range: 0000000000000...

...0000000fed14000 (reserved) BIOS-e820: 00000000fed18000 - 00000000fed1a000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff980000 - 00000000ffc00000 (reserved) BIOS-e820: 00000000ffd80000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 000000044f800000 (usable) DMI 2.6 present. SMBIOS version 2.6 @ 0xF0460 DMI: ASUSTeK Computer Inc. N55SL/N55SL, BIOS N55SL.201 11/10/2011 AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000...

...en: 0000000000100000 - 0000000010000000 (usable) [ 0.000000] Xen: 0000000010000000 - 000000007fef0000 (unusable) [ 0.000000] Xen: 000000007fef0000 - 000000007fef3000 (ACPI NVS) [ 0.000000] Xen: 000000007fef3000 - 000000007ff00000 (ACPI data) [ 0.000000] Xen: 00000000fec00000 - 0000000100000000 (reserved) [ 0.000000] Xen: 0000000100000000 - 000000016fef0000 (usable) On DOMUs I can ''fix'' this by adding ''memmap=0x800000$0x100000000'' to the kernel command line, which changes [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] Xen: 000000...

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

Hi! We have a problem that the dom0 very often does not boot and hangs in the hypervisor - see screenshot. The last message is: (XEN) Dom0 has maximum 16 VCPUs (afterwards xen should overwrite the memory) We are using the xen kernel from kernel.org git. Kernel is 2.6.32.24-xen with Xen 4.0.1 Hardware is HP DL380. Is this a known problem? Any hints what could be the problem and how we can

...(XEN) 00000000d7e8e000 - 00000000d7e90000 type 9 (XEN) 00000000d7e90000 - 00000000d7eb4000 (ACPI data) (XEN) 00000000d7eb4000 - 00000000d7ee0000 (ACPI NVS) (XEN) 00000000d7ee0000 - 00000000d8000000 (reserved) (XEN) 00000000e0000000 - 00000000f0000000 (reserved) (XEN) 00000000ffe00000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000428000000 (usable) (XEN) ACPI: RSDP 000FA320, 0024 (r2 ACPIAM) (XEN) ACPI: XSDT D7E90100, 008C (r1 SMCI 20100909 MSFT 97) (XEN) ACPI: FACP D7E90290, 00F4 (r4 090910 FACP2028 20100909 MSFT 97) (XEN) ACPI: DSDT D7E90670, 6E54 (r2 1BC...

The XenPVHVM extensions have not been tested much on very old hypervisors. At least Xen 3.4 gets some testing with the pvops kernel. Require at least Xen 3.4 for the PVonHVM extensions. If an older hypervisor is detected the extensions will be disabled and the guest will only see emulated hardware. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- arch/x86/xen/enlighten.c | 27

Hi, I have a problem with a dom0 which is unable to launch my domU : all my dom0 are Debian Lenny amd64 with Debian kernel 2.6.26-2-xen-amd64 and xen-hypervisor-3.2-1-amd64. Then all domU (PV) are Debian Lenny amd64 too, with vanilla kernel 2.6.29.6. So, this new dom0 can''t launch any domU which are working on an other dom0. Software is same on both dom0, and hardware is near the

...00000000bae3a000 (reserved) BIOS-e820: 00000000bae3a000 - 00000000bae7d000 (ACPI NVS) BIOS-e820: 00000000bae7d000 - 00000000bb000000 (usable) BIOS-e820: 00000000bb800000 - 00000000bfa00000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 000000043fe00000 (usable) DMI 2.6 present. SMBIOS version 2.6 @ 0xF0450 AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) e820 update range: 0000000000000000 - 0...

...0000000bf7d0000 - 00000000bf7e0000 (reserved) BIOS-e820: 00000000bf7ed000 - 00000000c0000000 (reserved) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fed20000 - 00000000fed40000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 0000000100000000 - 0000000440000000 (usable) DMI present. AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved) e820 remove range: 00000000000...

...00000000bae3a000 (reserved) BIOS-e820: 00000000bae3a000 - 00000000bae7d000 (ACPI NVS) BIOS-e820: 00000000bae7d000 - 00000000bb000000 (usable) BIOS-e820: 00000000bb800000 - 00000000bfa00000 (reserved) BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 000000083fe00000 (usable) DMI 2.6 present. SMBIOS version 2.6 @ 0xF0450 DMI: System manufacturer System Product Name/P8H67-M PRO, BIOS 1004 06/08/2011 AMI BIOS detected: BIOS may corrupt low RAM, working around it. e820 update range: 0000000000000000 - 0000...

I was using my computer normally when suddenly my btrfs volume became read-only. This is on Chris'' for-linus branch (latest commit cb77fcd88) Here''s the relevant excerpt from dmesg [ 50.877500] r8169 0000:01:00.0: eth1: link up [ 50.880296] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 60.959215] eth1: no IPv6 routers present [ 1904.463247] atkbd serio0: Unknown key