search for: acknowledg

...ICMP Echo (ping) request 2.034575 00:1b:78:05:84:6c -> Supermic_34:26:12 ARP 213.180.194.116 is at 00:1b:78:05:84:6c 2.034933 213.180.194.120 -> 213.180.194.116 TFTP Read Request, File: pxelinux/pxelinux.0, Transfer type: octet 2.035562 213.180.194.116 -> 213.180.194.120 TFTP Option Acknowledgement 2.036066 213.180.194.120 -> 213.180.194.116 TFTP Error Code, Code: Not defined, Message: TFTP Aborted 2.036184 213.180.194.120 -> 213.180.194.116 TFTP Read Request, File: pxelinux/pxelinux.0, Transfer type: octet 2.036808 213.180.194.116 -> 213.180.194.120 TFTP Data Packet, Bloc...

...("Local/517@sip-007f,2", "SIP/517|30|t") in new stack -- Called 517 -- SIP/517-39f4 is ringing -- Agent/4000 is ringing -- SIP/517-39f4 answered Local/517@sip-007f,2 -- Agent/4000 stopped sounds -- Local/517@sip-007f,1 answered, waiting for '#' to acknowledge == Spawn extension (sip, 517, 1) exited non-zero on 'Local/517@sip-007f,2' -- SIP/517-39f4 acknowledged -- Agent/4000 answered SIP/518-6071 However, when I dial an Agent channel in version 1.0.9, the Agent on the other side acknowledges the call (by pressing #), a transfer happe...

...client keeps sending the last ACK until it times out: No. Time Source Destination Protocol Info 2456 62.303446 10.4.253.5 10.4.253.206 TFTP Data Packet, Block: 1185 2457 62.303768 10.4.253.206 10.4.253.5 TFTP Acknowledgement, Block: 1185 2458 62.303782 10.4.253.5 10.4.253.206 TFTP Data Packet, Block: 1186 2459 62.304105 10.4.253.206 10.4.253.5 TFTP Acknowledgement, Block: 1186 2460 62.304120 10.4.253.5 10.4.253.206 TFTP Data Packet, B...

...gs, zttool, or the wanpipe tools. Intense pri debug output: < Unnumbered frame: < SAPI: 00 C/R: 1 EA: 0 < TEI: 000 EA: 1 < M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended ) ] < 0 bytes of data -- Got SABME from network peer. Sending Unnumbered Acknowledgement > [ 02 01 73 ] > Unnumbered frame: > SAPI: 00 C/R: 1 EA: 0 > TEI: 000 EA: 1 > M3: 3 P/F: 1 M2: 0 11: 3 [ UA (unnumbered acknowledgement) ] > 0 bytes of data -- Restarting T203 counter q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921....

Hello. I have a problem with the native Android SIP client, not acknowledging the call. Sent a message to the list for some weeks ago containing a sip debug log, but it only got stuck in moderation queue due to too large size (and it said I would get a message if moderators rejected it, but did not get message and I don't think it got posted to list either) Th...

...plan I use 9|. which sends 9 plus the 10 digit number. Using Wireshark to look at the QSIG commands coming from a Sangoma wanpipemon trace I see the following for an Asterisk to Toshiba internal call. Asterisk -> SETUP Toshiba -> CALL PROCESSING Toshiba -> CONNECT Asterisk -> CONNECT ACKNOWLEDGE However when trying to dial 9 + number I received the following Asterisk -> SETUP Toshiba -> SETUP ACKNOWLEDGE Looking at http://tools.ietf.org/html/rfc4497 I see the following On receipt of a QSIG SETUP message containing no Sending complete information element and a number in the C...

...fg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks for these TFTP options set (from TFTPd server). tsize 0 and blksize 1408. What seems to confuse it is that it gets back both acknowledgements in the same TFTP option acknowledgement packet. That is, the TFTP server's option acknowledgement packet has tsize option acknowledgement (tsize = 145744) and also blksize option acknowledgement (blksize = 1408). In reading the archives, I see Gene recommends the atftpd TFTP server. So...

...d Sending Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended Sending Set Asynchronous Balanced Mode Extended -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:805 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED...

...h in this please? tail -f /var/log/asterisk/full *[2010-05-17 13:45:28] ERROR[8212] chan_zap.c: Asked to delete sched id -1???* *[2010-05-17 13:45:28] ERROR[8212] chan_zap.c: No more room in scheduler* pri debug span 1 (repeats continuously): *-- Got SABME from network peer.* *Sending Unnumbered Acknowledgement* pri intense debug span 1 (repeats continuously): *< [ 02 01 7f ]* *pbx*CLI>* *< Unnumbered frame:* *< SAPI: 00 C/R: 1 EA: 0* *< TEI: 000 EA: 1* *< M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ]* *< 0 bytes of data* *Handling m...

...tion Protocol Length Info 15002 0.274814 10.4.0.1 10.4.255.254 TFTP 105 Read Request, File: efi64/images/default-image/initrd, Transfer type: octet, tsize\000=0\000, blksize\000=1408\000 15003 0.001082 10.4.255.254 10.4.0.1 TFTP 72 Option Acknowledgement, tsize\000=13442875\000, blksize\000=1408\000 15004 0.003735 10.4.0.1 10.4.255.254 TFTP 60 Acknowledgement, Block: 0 15005 0.000081 10.4.255.254 10.4.0.1 TFTP 1454 Data Packet, Block: 1 15006 0.000236 10.4.0.1 10.4.255.254...

R-devel, I've received permission from a third party to incorporate some of their data in a data set in my 'portfolio' package. I'd like to include an acknowledgment of the third party, and perhaps a "used with permission" somewhere in the package documentation. Where's the best spot in the package docs for such an acknowledgment? Is there a place preferable to the \description or \source sections of the data set's .Rd file? Thanks in ad...

...gth Info > 15002 0.274814 10.4.0.1 10.4.255.254 TFTP > 105 Read Request, File: efi64/images/default-image/initrd, Transfer > type: octet, tsize\000=0\000, blksize\000=1408\000 > 15003 0.001082 10.4.255.254 10.4.0.1 TFTP > 72 Option Acknowledgement, tsize\000=13442875\000, > blksize\000=1408\000 > 15004 0.003735 10.4.0.1 10.4.255.254 TFTP > 60 Acknowledgement, Block: 0 > 15005 0.000081 10.4.255.254 10.4.0.1 TFTP > 1454 Data Packet, Block: 1 > 15006 0.000236 10.4.0...

On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> ---...

On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin <mst at redhat.com> ---...

...ARP Who has 192.168.1.93? Tell 192.168.1.23 2159.841871 tuner.rotzorg.org -> ViaTechn_ca:68:a5 ARP 192.168.1.93 is at 00:10:4b:2a:ce:2f 2159.841974 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File: pxelinux.0, Transfer type: octet 2159.843251 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement 2159.843363 192.168.1.23 -> 192.168.1.93 TFTP Error Code, Code: Not defined, Message: TFTP Aborted 2159.844558 192.168.1.23 -> 192.168.1.93 TFTP Read Request, File: pxelinux.0, Transfer type: octet 2159.845581 192.168.1.93 -> 192.168.1.23 TFTP Option Acknowledgement 2159.845691 192.16...

...0616 192.168.0.112 192.168.0.1 TFTP Read Request, File: pxegrub, Transfer type: octet 148 13.678526 128.97.176.200 192.168.0.112 UDP Source port: 33184 Destination port: 32802 149 13.679517 192.168.0.112 192.168.0.1 TFTP Acknowledgement, Block: 1 150 13.679707 192.168.0.1 192.168.0.112 ICMP Destination unreachable 151 14.674531 128.97.176.200 192.168.0.112 UDP Source port: 33184 Destination port: 32802 152 14.675565 192.168.0.112 192.168.0.1 TFTP...

...d lawsuits and redundancy > > >> This is esp true of any VoIP PBX system. In fact I think many of them >> run Windows. >> > > Or VOIP in general. This is what Vonage makes you agree to in their > Terms of Service. > > "2.4 Requires Activation: > You acknowledge and understand that 911 dialing does not function > unless you have successfully activated the 911dialing feature by > following the instructions from the "Dial 911" link on your dashboard, > and until such later date that such activation has been > confirmed to you through...

...been modified by RedFone to add the ztd-ethmf module. My interface is a RedFone foneBridge2 4 Span; and I'm connecting to a BT E1 PRI / ISDN30e with 15 lines on span 1, and a legacy Panasonic PBX on span 4. Upon connection of the E1 I get the following in pri debug span 1: Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921.c:664 q921_dchannel_up: q921_state now is Q921_LINK_CONNECTION_ESTABLISHED -- Got SABME from network peer. Sending Unnumbered Acknowledgement q921.c:709 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED q921....

I keep getting repeated copies of ``R-help post acknowledgements'' in respect of a couple of postings that I made to the list this morning (my time). I only posted each posting *once*. I hope that others are not getting repeated copies of my postings .... I mean I *know* my postings are so wonderful they merit re-reading, but one does not need a...

Hi guys, Fosdem 2019 is slowly approaching and so they opened the registration form for participants and also stands requests. So it's now done for CentOS and let's see how that goes -------- Forwarded Message -------- Subject: Acknowledging your stand request (CentOS) Date: Tue, 14 Aug 2018 09:33:10 +0200 (CEST) From: stands at fosdem.org To: arrfab at centos.org CC: stands at fosdem.org Stand Request for FOSDEM 2019 We acknowledge that we have received your request for the following stand. After we review all stands requests, we...