[asterisk-users] Setting span orders with Astribank and Sangoma A101
Hi All Just a quick check on the best way to ensure multiple cards/devices load in the correct order. Asterisk 1.8 with Sangoma A101 had no problems until we introduced an Astribank. root@pabx377:/etc/asterisk# dahdi_hardware -v usb:001/004 xpp_usb+ e4e4:1162 Astribank-modular FPGA-firmware LABEL=[usb:X1060395] CONNECTOR=@usb-:00:1d.7-3 XBUS-00/XPD-00: FXS (14) Span 2 XBUS-00/XPD-10: FXS (8) Span 3 XBUS-00/XPD-20: FXS (8) Span 4 XBUS-00/XPD-30: FXS (8) Span 5 pci::05:00.0 wanpipe- 1923:0300 Sangoma Technologies Corp. A101 single-port T1/E1 But now they have changed order after reboot to 1-4 and I am guessing that makes the A101 span 5 but I want to make these setting permanent I see mention of /etc/dahdi/xpp_order and dahdi_genconf xpporder but will that help me set the spans within Dahdi so they always appear on the same number Thanks very much Cheers Duncan-- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Running Asterisk on VMware ESX
On 8/6/12 9:17 pm, Hiers, Richard wrote: I don't expect to need to use any special hardware, just a sip trunk over our broadband connection. We have about 150 phones at present. Is ESX a viable platform for us? And second, what is the recommended virtual configuration (mem, cpu, etc.)? Any other considerations? I think the concern expressed about running Asterisk on a virtualised platform is more to do with the impact the other load on the host machine might have on your Asterisk VM. If you're using ESX in a shared hosting environment where you have very little control over the other workload on that host, then sooner or later there's a risk your VM is going to experience spikes in latency. On the other hand, if you're running a virtualised platform internally where you can control precisely the load on the host machine, then you'll probably find you're fine. FWIW, we run Asterisk under Xen in production. Some of the VMs have well over a thousand connected SIP devices and we've yet to encounter significant problems. But we're able to control the other VMs on the hosts very precisely: the only other VMs running on those hosts provide low-load services such as rsync for remote backup (which is only used late at night when call load is low on the Asterisk VMs). Running Asterisk in a VM, even if it's the only VM on that host, does give you some considerable benefits in the event of host machine failover: hardware independence and live migration are the two that spring immediately to mind. Kind regards, Chris -- This email is made from 100% recycled electrons -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Running Asterisk on VMware ESX
The problem we ended up having with virtualised asterisk (on esx, xenserver and hyperv) was that the clock timings to the vm aren't always accurate when you're using dahdi_dummy. We had a bunch of voice quaity issues which took ages to diagnose because of this. Obviously if you have a DAHDI card that your passing through to the vm or one of these http://wiki.sangoma.com/sangoma-wanpipe-voicetime you can avoid this. -Blake On 11/06/12 5:07 AM, Chris Bagnall aster...@lists.minotaur.cc wrote: On 8/6/12 9:17 pm, Hiers, Richard wrote: I don't expect to need to use any special hardware, just a sip trunk over our broadband connection. We have about 150 phones at present. Is ESX a viable platform for us? And second, what is the recommended virtual configuration (mem, cpu, etc.)? Any other considerations? I think the concern expressed about running Asterisk on a virtualised platform is more to do with the impact the other load on the host machine might have on your Asterisk VM. If you're using ESX in a shared hosting environment where you have very little control over the other workload on that host, then sooner or later there's a risk your VM is going to experience spikes in latency. On the other hand, if you're running a virtualised platform internally where you can control precisely the load on the host machine, then you'll probably find you're fine. FWIW, we run Asterisk under Xen in production. Some of the VMs have well over a thousand connected SIP devices and we've yet to encounter significant problems. But we're able to control the other VMs on the hosts very precisely: the only other VMs running on those hosts provide low-load services such as rsync for remote backup (which is only used late at night when call load is low on the Asterisk VMs). Running Asterisk in a VM, even if it's the only VM on that host, does give you some considerable benefits in the event of host machine failover: hardware independence and live migration are the two that spring immediately to mind. Kind regards, Chris -- This email is made from 100% recycled electrons -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
