<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54187/possible-issues-with-edrx-on-verizon</link><description>Using the nRF9160 on the Verizon network we are having some issues with eDRX. Specifically sending data to the device from our MQTT server. 
 We have configured a eDRX interval of 40.96 seconds with a PTW of 1.28 seconds. What I&amp;#39;m seeing is that the socket</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 13 Dec 2019 13:45:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54187/possible-issues-with-edrx-on-verizon" /><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/225381?ContentTypeID=1</link><pubDate>Fri, 13 Dec 2019 13:45:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4c9932b-d0cc-4113-b43f-c5455dc9ce20</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Joshua,&lt;/p&gt;
&lt;p&gt;A suggestion for a workaround to this could be that every time the UE device (nrf91) is going to do any communication it can send an empty MQTT packet to the server on a specific topic then the server responds accordingly with the correct data so you do not lose any packets.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;NOTE: With the mfw1.1.0 the introduction of the&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Fpacket_domain%2Fcscon_set.html&amp;amp;resultof=%22%63%73%63%6f%6e%22%20" rel="noopener noreferrer" target="_blank"&gt; AT+CSCON command c&lt;/a&gt;an be used to get notifications when RRC Connections are established.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/224802?ContentTypeID=1</link><pubDate>Tue, 10 Dec 2019 18:06:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ed0199ae-c08f-4b8c-add2-a9d6dc195cbb</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;I have some additional information about how the Verizon network handles server to UE data.&amp;nbsp; Verizon is telling us that the network does not buffer any TCP to the UE, but they do buffer that they need to send a page to the UE.&amp;nbsp; After the UE receives the page, it will establish a RRC connection, but it is up to the server to deliver a TCP packet in the RRC window.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The issue is that the TCP server does not know when the UE has been paged.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It is possible for the nRF9160 to tell out application that it has been paged?&amp;nbsp; If so we could then send a message tot he server requesting data.&amp;nbsp; This could be a work around for the problem.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Since we are trying to implement bidirectional MQTT data, the current implementation of eDRX by Verizon basically makes server initiated TCP data useless, unless we can figure out a way to work around this issue.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thank you for the help.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/223480?ContentTypeID=1</link><pubDate>Wed, 04 Dec 2019 07:48:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2093c9ea-5406-41cc-8a83-4e599092769f</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;/p&gt;
&lt;p&gt;The issue seen in these logs is that the network is paging the UE (nRF91) and RRC connection gets established but the network does not send any data, just releases connection after a few seconds.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Martin L.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/223377?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2019 14:49:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ea53334-5c96-470d-8b8f-847fac3a499a</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;Hi Martin,&lt;/p&gt;
&lt;p&gt;Thanks for the response.&amp;nbsp; Do you have any additional details about what the traces show that I could share with the carrier to help pinpoint the issue?&amp;nbsp; Any specifics you would provide would be helpful.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/223376?ContentTypeID=1</link><pubDate>Tue, 03 Dec 2019 14:46:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:66538840-5915-4d20-b7b1-b0e50a6ea61f</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;/p&gt;
&lt;p&gt;I am sorry for the wait.&amp;nbsp;&lt;br /&gt;From analyzing the logs from the modem traces we can clearly see that the issue is on the network side.&lt;/p&gt;
&lt;p&gt;Please please push Verizon on this, since the issue is on the Network vendor side.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Martin L.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/222183?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2019 20:04:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab224279-153f-45cf-b8af-0001b52a8a4e</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I have re-run the tests using the 1.1.0 Modem firmware with the same results.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Packet traces are attached.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;During the&amp;nbsp;&amp;quot;trace-2019-11-26T19-49-11.648Z-eDRX no PKT.bin&amp;quot; I saw the nRF9160 wake up for two consecutive eDRX cycles, but it failed to receive the packet.&amp;nbsp; Again once this happens the connection from the server to the nRF9160 stops working until we close/re-open the socket.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;trace-2019-11-26T19-55-04.350Z-eDRX PKT received.bin&amp;quot; shows a packet being successfully received from the server and the socket remains functional.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you,&lt;/p&gt;
&lt;p&gt;Josh&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_26T19_2D00_55_2D00_04.350Z_2D00_eDRX-PKT-received.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_26T19_2D00_55_2D00_04.350Z_2D00_eDRX-PKT-received.bin&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_26T19_2D00_49_2D00_11.648Z_2D00_eDRX-no-PKT.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_26T19_2D00_49_2D00_11.648Z_2D00_eDRX-no-PKT.bin&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/221950?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2019 22:25:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d2ca8ef3-e1e1-4d4e-a9ef-57d771b7a2f7</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;Thank you for the response.&amp;nbsp; We will do additional testing with the 1.1.0 Modem firmware and let you know if we are still seeing this issue.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/221893?ContentTypeID=1</link><pubDate>Mon, 25 Nov 2019 14:40:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2c2238f-efb5-420a-9701-a3faed68a2ee</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://www.nordicsemi.com/Products/Low-power-cellular-IoT/nRF9160/Download#infotabs" rel="noopener noreferrer" target="_blank"&gt;modem firmware version 1.1.0 &lt;/a&gt;has been released with a lot of improvements and features.&lt;br /&gt;If possible, I would recommend you to update to the latest version and see if that improves the performance.&lt;/p&gt;
&lt;p&gt;If not, please attach the modem trace using the new modem firmware.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Martin L.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220950?ContentTypeID=1</link><pubDate>Tue, 19 Nov 2019 21:45:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2885362-c5c0-41b3-a009-5eb3ba9e6cca</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_19T21_2D00_06_2D00_32.613Z_2D00_eDRX-No-Pkt-received.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_19T21_2D00_06_2D00_32.613Z_2D00_eDRX-No-Pkt-received.bin&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_19T21_2D00_22_2D00_53.883Z_2D00_eDRX-Pkt-received-ok.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_19T21_2D00_22_2D00_53.883Z_2D00_eDRX-Pkt-received-ok.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Attached is another pair of captures this time from the USB port on the DK.&amp;nbsp; Hopefully these work.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220824?ContentTypeID=1</link><pubDate>Tue, 19 Nov 2019 12:23:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f727a7e8-5983-4f9a-b292-cd2a81c0bf8a</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;/p&gt;
&lt;p&gt;I am sorry for the delay.&lt;/p&gt;
&lt;p&gt;Unfortunatly the log is still invalid.&lt;/p&gt;
&lt;p&gt;Please repeat the test on a DK so we could get a valid modem trace from that device.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Martin L.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220147?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2019 16:13:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5cd638c2-2e8a-4ea0-b0d3-f8f77d418b6d</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_14T15_2D00_46_2D00_05.849Z_2D00_eDRX-issue.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_14T15_2D00_46_2D00_05.849Z_2D00_eDRX-issue.bin&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_14T16_2D00_05_2D00_12.839Z_2D00_eDRX-issue.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_14T16_2D00_05_2D00_12.839Z_2D00_eDRX-issue.bin&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_14T16_2D00_10_2D00_11.203Z_2D00_eDRX-OK.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_14T16_2D00_10_2D00_11.203Z_2D00_eDRX-OK.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s see if these are better.&amp;nbsp; If not we can get setup to run the same capture on the &lt;span&gt;nRF91DK&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220120?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2019 14:54:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4950b65f-bbe6-40f0-9d62-c2e5d7fccdba</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;I was using a custom board with external UART with a FTDI cable, which we have used successfully before.&amp;nbsp; But I was using a older laptop for logging this time, so I&amp;#39;ll change that out and see if it improves things.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220116?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2019 14:42:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c4524f2-d402-4861-a3c6-ce202ea7f352</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;/p&gt;
&lt;p&gt;Yes, that would be great.&amp;nbsp;&lt;br /&gt;Are you taking the modem traces from the nRF91DK or a custom board?&lt;/p&gt;
&lt;p&gt;from the VCOM or external UART with an FTDI cable?&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The issue could be the UART.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you are using the l&lt;a href="https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/drivers/lte_link_control" rel="noopener noreferrer" target="_blank"&gt;te_lc.c driver, &lt;/a&gt;it should be sufficient to put:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;CONFIG_BSD_LIBRARY_TRACE_ENABLED=y&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;in the prj.conf file of your application.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/220099?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2019 14:15:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f55d1f79-711d-476f-ac0f-d82daf7feb90</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;I did confirm that on the device I captured the logs on the reported modem firmware is mfw_nrf9160_1.0.1&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I will attempt to run the captures again today and see if they work for you.&amp;nbsp; Not sure why these would be invalid.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/219996?ContentTypeID=1</link><pubDate>Thu, 14 Nov 2019 08:31:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a50f09ba-35b7-4203-a8e9-26af9bb4664b</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;br /&gt;Could you please verify the modem firmware version? (&lt;em&gt;the logs cannot be decoded, most likely because of wrong modem firmware version)&lt;/em&gt;&lt;br /&gt;&lt;br /&gt;e.g. run at:_client (&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-9220eb5184c9476ba63f5f50df03289c/at_5F00_client.hex"&gt;devzone.nordicsemi.com/.../at_5F00_client.hex&lt;/a&gt;) with LTE Link Monitor and send the command &lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Fgeneral%2Fcgmr_set.html" rel="noopener noreferrer" target="_blank"&gt;AT+CGMR&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-9220eb5184c9476ba63f5f50df03289c/pastedimage1573720221319v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/219539?ContentTypeID=1</link><pubDate>Mon, 11 Nov 2019 18:17:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f463c71-90c5-4ed7-b65a-487ef537a6c5</guid><dc:creator>Joshua</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_11T18_2D00_11_2D00_06.562Z_2D00_edrx-rx-ok.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_11T18_2D00_11_2D00_06.562Z_2D00_edrx-rx-ok.bin&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/trace_2D00_2019_2D00_11_2D00_11T17_2D00_02_2D00_28.824Z_2D00_edrx-rx-issue.bin"&gt;devzone.nordicsemi.com/.../trace_2D00_2019_2D00_11_2D00_11T17_2D00_02_2D00_28.824Z_2D00_edrx-rx-issue.bin&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Attached are two trace files.&amp;nbsp; One with showing the receive issue and one showing a successful eDRX receive.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We are running modem firmware version 1.0.1&lt;/p&gt;
&lt;p&gt;Verizon is attempting to do a packet trace on their end as well and I&amp;#39;ll update this with any information I receive.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Possible issues with eDRX on Verizon</title><link>https://devzone.nordicsemi.com/thread/219499?ContentTypeID=1</link><pubDate>Mon, 11 Nov 2019 14:04:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ac8beac6-3520-4c22-8e38-e30f088216c3</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Josh,&lt;br /&gt;&lt;br /&gt;Please state which modem firmware version and SIM card you are using.&lt;/p&gt;
&lt;p&gt;Please take a &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect" rel="noopener noreferrer" target="_blank"&gt;modemtrace so we could&lt;/a&gt;&amp;nbsp;investigate the issue in more detail.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>