Re: [asterisk-users] Issues with Xorcom astribanks when running Ubuntu 11.10 (oneiric) as a quemu/libvirt guest
Tzafrir, I am in front of the server. Le dimanche 30 octobre 2011 à 22:13 +0100, Eric van der Vlist a écrit : Tzafrir, Le dimanche 30 octobre 2011 à 10:30 +0200, Tzafrir Cohen a écrit : The problem is elsewhere. What happens if you manually run: /usr/share/dahdi/xpp_fxloader load #? vdv@asterisk-rg:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID e4e4:1161 Xorcom Ltd. Astribank 2 series vdv@asterisk-rg:~$ sudo /usr/share/dahdi/xpp_fxloader load [sudo] password for vdv: 'xpp_fxloader'[850]: - FIRMWARE LOADING: (load) [1 devices] Got all 1 devices INFO: usb:001/003: ID=E4E4:1161 [Xorcom LTD / Astribank / X1047833] INFO: Loading hexfile to FPGA: /usr/share/dahdi/FPGA_1161.hex (version 7276) mpp_funcs.c:308: ERROR(recv_command): Receive from usb failed. mpp_funcs.c:359: ERROR(process_command): recv_command failed mpp_funcs.c:710: ERROR(mpp_send_start): process_command failed: -71 astribank_hexload.c:99: ERROR(load_hexfile): Failed hexfile send start: -71 astribank_hexload.c:218: ERROR(main): Loading firmware to FPGA failed 'xpp_fxloader'[898]: /usr/sbin/astribank_hexload failed with status 1 Or: astribank_tool -D 001/005 -Q I'll test that as soon as I can! If you have dahdi-tools 2.5, you'll need: astribank_tool -D /dev/bun/usb/001/005 -Q vdv@asterisk-rg:~$ sudo astribank_tool -D /dev/bus/usb/001/003 -Q mpp_funcs.c:308: ERROR(recv_command): Receive from usb failed. mpp_funcs.c:359: ERROR(process_command): recv_command failed mpp_funcs.c:454: ERROR(mpp_proto_query): process_command failed: -71 mpp_funcs.c:1001: ERROR(mpp_init): Protocol handshake failed: -71 astribank_tool.c:209: ERROR(main): Failed initializing MPP What version of dahdi-tools is it? 2.4.1, and I see that dahdi-firmware-nonfree (that includes your firmware) is 2.2.1.1-1: vdv@lrt-rg:~$ dpkg -l *dahdi* Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Description +++--- ii asterisk-dahdi 1:1.8.4.4~dfsg-2ubuntu1 DAHDI devices support for the Asterisk PBX ii dahdi1:2.4.1-1ubuntu1 utilities for using the DAHDI kernel modules ii dahdi-dkms 1:2.4.1+dfsg-1ubuntu2DAHDI telephony interface (dkms kernel driver) ii dahdi-firmware-nonfree 2.2.1.1-1DAHDI non-free firmware ii dahdi-linux 1:2.4.1+dfsg-1ubuntu2DAHDI telephony interface - Linux userspace parts un dahdi-source none (aucune description n'est disponible) That being said, the host (in which the firmware loads fine) has exactly the same versions installed. Thanks for your help, Eric -- _ -- 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] Issues with Xorcom astribanks when running Ubuntu 11.10 (oneiric) as a quemu/libvirt guest
Tzafrir, Le dimanche 30 octobre 2011 à 10:30 +0200, Tzafrir Cohen a écrit : On Sat, Oct 29, 2011 at 08:14:55PM +0200, Eric van der Vlist wrote: Hi, Xorcom astribanks get initialized straight on when using Ubuntu 11.10 packages but I am having a hard time to get the same result running in a qemu/libvirt image. qemu? qemu+kqemu (the kernel module)? kvm? I would expect plain qemu to have pretty bad performance, though I hardly tried to use it lately. I am using qemu-kvm right now but I am open to other open source alternatives! Anyway, it should be more than enough for the simple firmware loading step. The first difficulty is that astribanks devices get different usb device ids during their initialisation process, requiring hot plug support. I have figured out how to solve this issue using the technique described in this post : http://www.blogs.uni-osnabrueck.de/rotapken/2011/04/11/how-to-auto-hotplug-usb-devices-to-libvirt-vms/ That doesn't seem to be enough and the initialisation fails with a status 1: Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1006]: Trying to find what to do for product e4e4/1160/101, device /dev/bus/usb/001/004 Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1010]: Loading firmware '/usr/share/dahdi/USB_FW.hex' into '/dev/bus/usb/001/004' That's good. Oct 28 18:58:23 asterisk-rg 'xpp_fxloader'[1024]: Trying to find what to do for product e4e4/1161/101, device /dev/bus/usb/001/005 Oct 28 18:58:34 asterisk-rg 'xpp_fxloader'[1035]: /usr/sbin/astribank_tool failed with status 1 Seeing that Xorcom requires USB 2.0 Technically the Astribank driver requires USB 2.0 as it was not worth it to adapt it to the maximal URB (messagee) size of 64 byte of USB 1.1. astribank_hexload actually was never adapted to that limitation either. While this may be considered a bug, we hardly needed to load the firmware on USB 1.1 and this gets an earlier and safer fail on most cases. Anyway, astribank_tool does not use large USB messages. I would not expect it to fail on USB 1.1 . My assumption that this could be the cause of my issues was based on this blog post : http://www.parnreiter.at/xorcom-astribank.aspx. The error messages I got were very close to those mentioned in that page, especially these ones: astribank_hexload.c:99: ERROR(load_hexfile): Failed hexfile send start: -71 astribank_hexload.c:218: ERROR(main): Loading firmware to FPGA failed 'xpp_fxloader'[23554]: /usr/sbin/astribank_hexload failed with status 1 I am not in front of the server right now and can't test it again, but from memory I *think* that the error message was the same except from the value -71 which was more like -73 in my case. The problem is elsewhere. What happens if you manually run: /usr/share/dahdi/xpp_fxloader load #? Or: astribank_tool -D 001/005 -Q I'll test that as soon as I can! If you have dahdi-tools 2.5, you'll need: astribank_tool -D /dev/bun/usb/001/005 -Q and that the current versions of libvirt and qemu in Ubuntu 11.10 emulate USB 1.10 in guests, I have installed Boris Derzhavets' packages: https://launchpad.net/~bderzhavets/+archive/seabios163 and updated my host definition to emulate USB 2.0 but I still have the same issue. Have I missed something? What version of dahdi-tools is it? 2.4.1, and I see that dahdi-firmware-nonfree (that includes your firmware) is 2.2.1.1-1: vdv@lrt-rg:~$ dpkg -l *dahdi* Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Description +++--- ii asterisk-dahdi 1:1.8.4.4~dfsg-2ubuntu1 DAHDI devices support for the Asterisk PBX ii dahdi1:2.4.1-1ubuntu1 utilities for using the DAHDI kernel modules ii dahdi-dkms 1:2.4.1+dfsg-1ubuntu2DAHDI telephony interface (dkms kernel driver) ii dahdi-firmware-nonfree 2.2.1.1-1DAHDI non-free firmware ii dahdi-linux 1:2.4.1+dfsg-1ubuntu2DAHDI telephony interface - Linux userspace parts un dahdi-source none (aucune description n'est disponible) That being said, the host (in which the firmware loads fine) has exactly the same versions installed. Thanks for your help, Eric -- _ -- 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
[asterisk-users] Issues with Xorcom astribanks when running Ubuntu 11.10 (oneiric) as a quemu/libvirt guest
Hi, Xorcom astribanks get initialized straight on when using Ubuntu 11.10 packages but I am having a hard time to get the same result running in a qemu/libvirt image. The first difficulty is that astribanks devices get different usb device ids during their initialisation process, requiring hot plug support. I have figured out how to solve this issue using the technique described in this post : http://www.blogs.uni-osnabrueck.de/rotapken/2011/04/11/how-to-auto-hotplug-usb-devices-to-libvirt-vms/ That doesn't seem to be enough and the initialisation fails with a status 1: Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1006]: Trying to find what to do for product e4e4/1160/101, device /dev/bus/usb/001/004 Oct 28 18:58:19 asterisk-rg 'xpp_fxloader'[1010]: Loading firmware '/usr/share/dahdi/USB_FW.hex' into '/dev/bus/usb/001/004' Oct 28 18:58:23 asterisk-rg 'xpp_fxloader'[1024]: Trying to find what to do for product e4e4/1161/101, device /dev/bus/usb/001/005 Oct 28 18:58:34 asterisk-rg 'xpp_fxloader'[1035]: /usr/sbin/astribank_tool failed with status 1 Seeing that Xorcom requires USB 2.0 and that the current versions of libvirt and qemu in Ubuntu 11.10 emulate USB 1.10 in guests, I have installed Boris Derzhavets' packages: https://launchpad.net/~bderzhavets/+archive/seabios163 and updated my host definition to emulate USB 2.0 but I still have the same issue. Have I missed something? Thanks, Eric -- _ -- 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] Xorcom Astribank udev issue in Ubuntu 9.10
Le samedi 14 novembre 2009 à 20:44 +0100, Eric van der Vlist a écrit : and playing with udevadm test, I have noticed that the following rule: +++ KERNEL==[0-9]*, GOTO=xpp_usb_add_end +++ is always met and that if I comment it, the astribank get initialized. Is that safe to remove this rule or is there a better solution? I am doing some more tests and that rule really seems to be doing the difference. I also notice that even when that rule is commented, plugging an uninitialized astribank after the server has been restarted doesn't seem to work: for whatever reason, when I try to load the dahdi module in asterisk I get this error message: asterisk*CLI module load chan_dahdi.so Unable to load module chan_dahdi.so Command 'module load chan_dahdi.so' failed. [Nov 15 11:10:45] WARNING[2640]: pbx.c:5048 ast_register_application2: Already have an application 'DAHDISendKeypadFacility' == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/dahdi-channels.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found [Nov 15 11:10:45] WARNING[2640]: chan_dahdi.c:2121 dahdi_open: Unable to specify channel 1: No such device or address [Nov 15 11:10:45] ERROR[2640]: chan_dahdi.c:10022 mkintf: Unable to open channel 1: No such device or address here = 0, tmp-channel = 1, channel = 1 [Nov 15 11:10:45] ERROR[2640]: chan_dahdi.c:15972 build_channels: Unable to register channel '1-2' This isn't a big deal since I won't be doing that so often on a production server, but that may be worth mentioning... Another weirdness is that dadhi tools keep complaining that /sys/bus/xpds/devices/00:0:0/timing_priority is missing: v...@asterisk:~$ sudo lsdahdi Use of uninitialized value $busnum in sprintf at /usr/local/share/perl/5.10.0/Dahdi/Hardware/USB.pm line 100. Use of uninitialized value $devnum in sprintf at /usr/local/share/perl/5.10.0/Dahdi/Hardware/USB.pm line 100. /usr/sbin/lsdahdi: warning - OLD DRIVER: missing '/sys/bus/xpds/devices/00:0:0/timing_priority'. Fall back to /proc ### Span 1: DAHDI_DUMMY/1 DAHDI_DUMMY/1 (source: HRtimer) 1 (MASTER) ### Span 2: XBUS-00/XPD-00 Xorcom XPD #00/00: BRI_NT AMI/CCS 1 BRI_NT Clear (In use) (SWEC: MG2) 2 BRI_NT Clear (In use) (SWEC: MG2) 3 BRI_NT Hardware-assisted HDLC (In use) ### Span 3: XBUS-00/XPD-01 Xorcom XPD #00/01: BRI_TE AMI/CCS 4 BRI_TE Clear (In use) (SWEC: MG2) 5 BRI_TE Clear (In use) (SWEC: MG2) 6 BRI_TE Hardware-assisted HDLC (In use) ### Span 4: XBUS-00/XPD-02 Xorcom XPD #00/02: BRI_NT AMI/CCS 7 BRI_NT Clear (In use) (SWEC: MG2) 8 BRI_NT Clear (In use) (SWEC: MG2) 9 BRI_NT Hardware-assisted HDLC (In use) ### Span 5: XBUS-00/XPD-03 Xorcom XPD #00/03: BRI_NT AMI/CCS 10 BRI_NT Clear (In use) (SWEC: MG2) 11 BRI_NT Clear (In use) (SWEC: MG2) 12 BRI_NT Hardware-assisted HDLC (In use) And: v...@asterisk:~$ ls /sys/bus/xpds/devices/00:0:0 blink chipregs driver offhook power span subsystem type uevent Also, I have always wondered why dahdi sees 4 spans when my astribank only has 2 BRIs! Thanks for your help, I would really like to know at least how safe it is to comment that rule! Eric -- Eric van der Vlist v...@dyomedea.com Dyomedea (http://dyomedea.com) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Sip incoming call issue with Asterisk 1.6
After a migration to asterisk 1.6, I don't receive sip incoming calls anymore. As fas as I understand the SIP debug traces, my server receives the request and reject it: ++ --- SIP read from UDP:212.27.52.5:5060 --- INVITE sip:s...@192.168.4.2:5060;transport=udp SIP/2.0 Call-ID: 25151-ww-0eaf098b-2f615a...@freephonie.net Contact: sip:172.17.20.241:5062 Content-Type: application/sdp CSeq: 239836027 INVITE From: 096160 sip:096160x...@freephonie.net;user=phone;tag=25151-GA-0eaf098c-32a97dc05 Max-Forwards: 28 Record-Route: sip:C=on-88.165.134.117.5060;t=rd...@212.27.52.5:5060;lr To: sip:095199y...@172.17.20.241;user=phone Via: SIP/2.0/UDP 212.27.52.5:5060;branch=z9hG4bK-RDKI-00720204-55801b4f Allow: UPDATE,REFER,INFO User-Agent: Cirpack/v4.41c (gw_sip) Content-Length: 173 v=0 o=cp10 125830752022 125830752022 IN IP4 212.27.52.129 s=SIP Call c=IN IP4 212.27.52.129 t=0 0 m=audio 36480 RTP/AVP 8 b=AS:64 a=rtpmap:8 PCMA/8000/1 a=ptime:30 - --- (13 headers 9 lines) --- == Using SIP RTP CoS mark 5 Sending to 212.27.52.5 : 5060 (no NAT) Using INVITE request as basis request - 25151-ww-0eaf098b-2f615a...@freephonie.net Found peer 'freephonie_appelsortant' for '096160' from 212.27.52.5:5060 asterisk*CLI --- Reliably Transmitting (no NAT) to 212.27.52.5:5060 --- SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 212.27.52.5:5060;branch=z9hG4bK-RDKI-00720204-55801b4f;received=212.27.52.5 From: 096160 sip:096160x...@freephonie.net;user=phone;tag=25151-GA-0eaf098c-32a97dc05 To: sip:095199y...@172.17.20.241;user=phone;tag=as03dcbe68 Call-ID: 25151-ww-0eaf098b-2f615a...@freephonie.net CSeq: 239836027 INVITE Server: Asterisk PBX 1.6.2.0~rc2-0ubuntu1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm=asterisk, nonce=78360854 Content-Length: 0 ++ Some googling kind of suggest that this might be because for my ISP my username is also my phone number: http://lists.digium.com/pipermail/asterisk-dev/2009-January/036259.html The problem arises since you use phone numbers as identifiers for the users. This is not a good thing (TM) and should be avoided. The dialplan is where you route phone numbers. Devices should have device names that you address in the dialplan on the extension that is supposed to connect to one or several devices. Am I right or must I search elsewhere? Whether it's a good thing or not, I doubt I can convince Free (http://free.fr) which is one of the biggest ISPs in France to change their policy so that I can receive SIP calls again... If my diagnostic is right, is there a way to work around this issue with asterisk 1.6? Thanks, Eric -- Eric van der Vlist v...@dyomedea.com Dyomedea (http://dyomedea.com) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Sip incoming call issue with Asterisk 1.6
Leif, Le dimanche 15 novembre 2009 à 16:18 -0500, Leif Madsen a écrit : I'm not sure you've provided enough of the trace here. It finds the peer, but rejects it with a 401 Unauthorized, which is not uncommon. And I don't see any authentication information in the first INVITE. This is why the 401 is sent back, as the WWW-Authenticate line contains the realm and nonce which should be used by the other end to generate the authentication, and then send another INVITE back with authentication. Since you've only shown the two packets in the trace, it is impossible to tell what is going on beyond the 401 response from Asterisk. Leif. I attach more packets (from a new test run). Thanks, Eric - --- (7 headers 0 lines) --- Really destroying SIP dialog '074e14720543d49c21e4999c4786b...@192.168.4.2' Method: OPTIONS asterisk*CLI --- SIP read from UDP:212.27.52.5:5060 --- INVITE sip:s...@192.168.4.2:5060;transport=udp SIP/2.0 Call-ID: 01749-lo-0eb4458a-552a13...@freephonie.net Contact: sip:172.17.20.241:5062 Content-Type: application/sdp CSeq: 240171363 INVITE From: Caller sip:095245x...@freephonie.net;user=phone;tag=01749-RV-0eb4458b-093bd4160 Max-Forwards: 28 Record-Route: sip:C=on-88.165.134.117.5060;t=xn...@212.27.52.5:5060;lr To: sip:095199y...@172.17.20.241;user=phone Via: SIP/2.0/UDP 212.27.52.5:5060;branch=z9hG4bK-XNJD-0079618e-344c12fe Allow: UPDATE,REFER,INFO User-Agent: Cirpack/v4.41c (gw_sip) Content-Length: 173 v=0 o=cp10 125832072268 125832072268 IN IP4 212.27.52.130 s=SIP Call c=IN IP4 212.27.52.130 t=0 0 m=audio 33092 RTP/AVP 8 b=AS:64 a=rtpmap:8 PCMA/8000/1 a=ptime:30 - --- (13 headers 9 lines) --- == Using SIP RTP CoS mark 5 Sending to 212.27.52.5 : 5060 (no NAT) Using INVITE request as basis request - 01749-lo-0eb4458a-552a13...@freephonie.net Found peer 'freephonie_appelsortant' for '095245' from 212.27.52.5:5060 asterisk*CLI --- Reliably Transmitting (no NAT) to 212.27.52.5:5060 --- SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 212.27.52.5:5060;branch=z9hG4bK-XNJD-0079618e-344c12fe;received=212.27.52.5 From: Caller sip:095245x...@freephonie.net;user=phone;tag=01749-RV-0eb4458b-093bd4160 To: sip:095199y...@172.17.20.241;user=phone;tag=as7249497d Call-ID: 01749-lo-0eb4458a-552a13...@freephonie.net CSeq: 240171363 INVITE Server: Asterisk PBX 1.6.2.0~rc2-0ubuntu1 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces, timer WWW-Authenticate: Digest algorithm=MD5, realm=asterisk, nonce=4a3516d7 Content-Length: 0 Scheduling destruction of SIP dialog '01749-lo-0eb4458a-552a13...@freephonie.net' in 6400 ms (Method: INVITE) asterisk*CLI --- SIP read from UDP:212.27.52.5:5060 --- ACK sip:s...@192.168.4.2:5060;transport=udp SIP/2.0 Call-ID: 01749-lo-0eb4458a-552a13...@freephonie.net CSeq: 240171363 ACK From: Caller sip:095245x...@freephonie.net;user=phone;tag=01749-RV-0eb4458b-093bd4160 Max-Forwards: 28 To: sip:095199y...@172.17.20.241;user=phone;tag=as7249497d Via: SIP/2.0/UDP 212.27.52.5:5060;branch=z9hG4bK-XNJD-0079618e-344c12fe Content-Length: 0 - --- (8 headers 0 lines) --- Really destroying SIP dialog '01749-lo-0eb4458a-552a13...@freephonie.net' Method: ACK Reliably Transmitting (no NAT) to 212.27.52.5:5060: OPTIONS sip:freephonie.net SIP/2.0 Via: SIP/2.0/UDP 192.168.4.2:5060;branch=z9hG4bK41486e10;rport Max-Forwards: 70 From: asterisk sip:aster...@192.168.4.2;tag=as096de98b To: sip:freephonie.net Contact: sip:aster...@192.168.4.2 Call-ID: 3334481068f263823a05fdef0480f...@192.168.4.2 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.6.2.0~rc2-0ubuntu1 Date: Sun, 15 Nov 2009 21:32:40 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces, timer Content-Length: 0 --- Reliably Transmitting (no NAT) to 212.27.52.5:5060: OPTIONS sip:freephonie.net SIP/2.0 Via: SIP/2.0/UDP 192.168.4.2:5060;branch=z9hG4bK49b10bb3;rport Max-Forwards: 70 From: asterisk sip:aster...@192.168.4.2;tag=as0c4787d3 To: sip:freephonie.net Contact: sip:aster...@192.168.4.2 Call-ID: 00cb37381237588a64cbe39a43ca0...@192.168.4.2 CSeq: 102 OPTIONS User-Agent: Asterisk PBX 1.6.2.0~rc2-0ubuntu1 Date: Sun, 15 Nov 2009 21:32:41 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO Supported: replaces, timer Content-Length: 0 --- asterisk*CLI --- SIP read from UDP:212.27.52.5:5060 --- SIP/2.0 501 Not Implemented Yet Call-ID: 3334481068f263823a05fdef0480f...@192.168.4.2 CSeq: 102 OPTIONS From: asterisk sip:aster...@192.168.4.2;tag=as096de98b To: sip:freephonie.net;tag=00-32733-00efde5e-4f3d2a1b6 Via: SIP/2.0/UDP 192.168.4.2:5060;received=88.165.134.117;rport=5060;branch=z9hG4bK41486e10 Content-Length: 0 - --- (7 headers 0 lines) --- Really destroying SIP dialog '3334481068f263823a05fdef0480f...@192.168.4.2' Method: OPTIONS asterisk*CLI --- SIP read from UDP:212.27.52.5:5060 --- SIP/2.0 501 Not Implemented Yet Call-ID:
Re: [asterisk-users] Sip incoming call issue with Asterisk 1.6
Leif, Le dimanche 15 novembre 2009 à 22:44 +0100, Eric van der Vlist a écrit : Leif, Le dimanche 15 novembre 2009 à 16:18 -0500, Leif Madsen a écrit : I'm not sure you've provided enough of the trace here. It finds the peer, but rejects it with a 401 Unauthorized, which is not uncommon. And I don't see any authentication information in the first INVITE. This is why the 401 is sent back, as the WWW-Authenticate line contains the realm and nonce which should be used by the other end to generate the authentication, and then send another INVITE back with authentication. After you've brought my attention to a potential authentication issue, I did some more researches in that direction and found out that I had been caught by this migration issue: http://forums.whirlpool.net.au/forum-replies-archive.cfm/1133054.html If I add insecure=port,invite declarations in my sip.conf, my incoming calls appear to come through. Weirdly, they seem to be coming from the context I am using to define outgoing calls rather than the one for ingoing ones (like in asterisk 1.4), but I guess that's another issue! Thanks, Eric -- Eric van der Vlist v...@dyomedea.com Dyomedea (http://dyomedea.com) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Sip incoming call issue with Asterisk 1.6
Le dimanche 15 novembre 2009 à 23:45 +0100, Eric van der Vlist a écrit : Weirdly, they seem to be coming from the context I am using to define outgoing calls rather than the one for ingoing ones (like in asterisk 1.4), but I guess that's another issue! Hmmm... I wonder where it can be documented but there seems to be a significant difference in the way I need to write my sip.conf in asterisk 1.4 and 1.6. In 1.4 I had to create two peers (one for outgoing and one for incoming calls). In 1.6 it appears that it just ignores the second peer and that I have to define only one peer for both directions (at least this is working for me). Fully solving my issue involved consolidating these two peers into one and adding an insecure=port,invite declaration. Eric -- Eric van der Vlist v...@dyomedea.com Dyomedea (http://dyomedea.com) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Xorcom Astribank udev issue in Ubuntu 9.10
Hi Tzafrir,
Le samedi 14 novembre 2009 à 21:30 +0200, Tzafrir Cohen a écrit :
On Sat, Nov 14, 2009 at 12:55:46AM +0100, Eric van der Vlist wrote:
Hi,
I have upgraded an Asterisk installation with a Xorcom BRI Astribank
that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no
longer initialized.
When I reload the udev rules, I see that the rules seems to be correctly
loaded:
udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file
What exactly do you have in that file?
I have:
+++
BUS!=usb, ACTION!=add, GOTO=xpp_usb_add_end
KERNEL==*_ep*, GOTO=xpp_usb_add_end
KERNEL==[0-9]*, GOTO=xpp_usb_add_end
# Load firmware into the Xorcom Astribank device:
SYSFS{idVendor}==e4e4, SYSFS{idProduct}==11[3456][01], \
RUN+=/usr/share/dahdi/xpp_fxloader udev
$sysfs{idVendor}/$sysfs{idProduct}/$sysfs{bcdDevice}
LABEL=xpp_usb_add_end
# Hotplug hook for Astribank up/down
# If you need this functionality, copy the astribank_hook.sample
# to $XPP_INIT_DIR/astribank_hook
#
# By default XPP_INIT_DIR=/usr/share/dahdi
KERNEL==xbus* RUN+=%E{XPP_INIT_DIR}/astribank_hook udev $kernel
$sysfs{status} $sysfs{connector}
+++
and playing with udevadm test, I have noticed that the following rule:
+++
KERNEL==[0-9]*, GOTO=xpp_usb_add_end
+++
is always met and that if I comment it, the astribank get initialized.
Is that safe to remove this rule or is there a better solution?
Thanks,
Eric
--
Eric van der Vlist v...@dyomedea.com
Dyomedea (http://dyomedea.com)
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Xorcom Astribank udev issue in Ubuntu 9.10
Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger --attr-match=idVendor=e4e4 --action add UDEV [1258155881.753357] add /devices/pci:00/:00:1a.7/usb1/1-1 (usb) UDEV_LOG=7 ACTION=add DEVPATH=/devices/pci:00/:00:1a.7/usb1/1-1 SUBSYSTEM=usb DEVNAME=/dev/bus/usb/001/009 DEVTYPE=usb_device DRIVER=usb DEVICE=/proc/bus/usb/001/009 PRODUCT=e4e4/1141/ TYPE=0/0/0 BUSNUM=001 DEVNUM=009 SEQNUM=1516 ID_VENDOR=Xorcom_LTD ID_VENDOR_ENC=Xorcom\x20LTD ID_VENDOR_ID=e4e4 ID_MODEL=Astribank ID_MODEL_ENC=Astribank ID_MODEL_ID=1141 ID_REVISION= ID_SERIAL=Xorcom_LTD_Astribank_ ID_SERIAL_SHORT= ID_BUS=usb ID_USB_INTERFACES=:ff: MAJOR=189 MINOR=8 DEVLINKS=/dev/char/189:8 Nov 14 00:44:41 asterisk udevd[452]: seq 1516 queued, 'add' 'usb' Nov 14 00:44:41 asterisk udevd[452]: passed 287 bytes to monitor 0xb94cf1f0 Nov 14 00:44:41 asterisk udevd-work[4995]: seq 1516 running Nov 14 00:44:41 asterisk udevd-work[4995]: device 0xb94d7700 has devpath '/devices/pci:00/:00:1a.7/usb1/1-1' Nov 14 00:44:41 asterisk udevd-work[4995]: IMPORT 'usb_id --export /devices/pci:00/:00:1a.7/usb1/1-1' /lib/udev/rules.d/40-libgphoto2-2.rules:11 Nov 14 00:44:41 asterisk udevd-work[4995]: 'usb_id --export /devices/pci:00/:00:1a.7/usb1/1-1' started Nov 14 00:44:41 asterisk usb_id[4997]: custom logging function 0xb80a5008 registered Nov 14 00:44:41 asterisk usb_id[4997]: device 0xb80a50e8 has devpath '/devices/pci:00/:00:1a.7/usb1/1-1' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR=Xorcom_LTD' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR_ENC=Xorcom\x20LTD' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_VENDOR_ID=e4e4' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_MODEL=Astribank' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_MODEL_ENC=Astribank' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_MODEL_ID=1141' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_REVISION=' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_SERIAL=Xorcom_LTD_Astribank_' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_SERIAL_SHORT=' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_BUS=usb' Nov 14 00:44:41 asterisk udevd-work[4995]: '/lib/udev/usb_id' (stdout) 'ID_USB_INTERFACES=:ff:' Nov 14 00:44:41 asterisk udevd-work[4995]: 'usb_id --export /devices/pci:00/:00:1a.7/usb1/1-1' returned with exitcode 0 Nov 14 00:44:41 asterisk udevd-work[4995]: device 0xb94decf8 has devpath '/devices/pci:00/:00:1a.7/usb1' Nov 14 00:44:41 asterisk udevd-work[4995]: device 0xb94df440 has devpath '/devices/pci:00/:00:1a.7' Nov 14 00:44:41 asterisk udevd-work[4995]: device 0xb94df5e0 has devpath '/devices/pci:00' Nov 14 00:44:41 asterisk udevd-work[4995]: LINK 'char/189:8' /lib/udev/rules.d/50-udev-default.rules:4 Nov 14 00:44:41 asterisk udevd-work[4995]: MODE 0664 /lib/udev/rules.d/50-udev-default.rules:58 Nov 14 00:44:41 asterisk udevd-work[4995]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Nov 14 00:44:41 asterisk udevd-work[4995]: no node name set, will use kernel supplied name 'bus/usb/001/009' Nov 14 00:44:41 asterisk udevd-work[4995]: created db file for '/devices/pci:00/:00:1a.7/usb1/1-1' in '/dev/.udev/db/usb:1-1' Nov 14 00:44:41 asterisk udevd-work[4995]: creating device node '/dev/bus/usb/001/009', devnum=189:8, mode=0664, uid=0, gid=0 Nov 14 00:44:41 asterisk udevd-work[4995]: mknod(/dev/bus/usb/001/009, 020664, (189,8)) Nov 14 00:44:41 asterisk udevd-work[4995]: chmod(/dev/bus/usb/001/009, 020664) Nov 14 00:44:41 asterisk udevd-work[4995]: chown(/dev/bus/usb/001/009, 0, 0) Nov 14 00:44:41 asterisk udevd-work[4995]: creating symlink '/dev/char/189:8' to '../bus/usb/001/009' Nov 14 00:44:41 asterisk udevd-work[4995]: passed 593 bytes to monitor 0xb94df948 Nov 14 00:44:41 asterisk udevd-work[4995]: passed -1 bytes to monitor 0xb94deb80 Nov 14 00:44:41 asterisk udevd-work[4995]: seq 1516 processed with 0 Nov 14 00:44:41 asterisk udevd[452]: seq 1516 done with 0 I have tried with the version of dahdi that comes with Ubuntu 9.10 and I am now trying with the svn version of dahdi with no more success. Does anyone have an idea how I can solve this issue? Thanks, Eric -- Eric van der Vlist v...@dyomedea.com Dyomedea (http://dyomedea.com
