Article View: alt.pl.voip
Article #73818Re: Ficzersy VoIP - jak zrealizować?
From: zlotowinfo
Date: Fri, 25 Nov 2016 18:08
Date: Fri, 25 Nov 2016 18:08
7 lines
1500 bytes
1500 bytes
Użytkownik "Krzysztof Burzyński" <krzysztof.burzynski@biznesinnovation.com> napisał w wiadomości news:47df4df2-b032-45ae-9afd-07739a45a07e@googlegroups.com... > Jednak nfon jeśli ma być support i niedrogo ;) > przecież ten nfon to jakaś porażka, tam są abonamenty a voip bierzemy po to by nie płacić abonamentów
Technical Details
Message-ID:
<o19unj$q8f$1@node1.news.atman.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mailReferences:
<8c9038f4-4943-4a83-bfd1-c7d81908eb66@googlegroups.com> <297d274c-fc66-4867-9234-09deb366f222@googlegroups.com> <nvl8cd$34g$1@node2.news.atman.pl> <nvmu80$m0q$1@node2.news.atman.pl> <47df4df2-b032-45ae-9afd-07739a45a07e@googlegroups.com>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!.POSTED!not-for-mail From: "zlotowinfo" <usuntousun@go2.pl> Newsgroups: alt.pl.voip Subject: Re: Ficzersy VoIP - jak zrealizować? Date: Fri, 25 Nov 2016 19:08:10 +0100 Organization: ATMAN - ATM S.A. Lines: 8 Message-ID: <o19unj$q8f$1@node1.news.atman.pl> References: <8c9038f4-4943-4a83-bfd1-c7d81908eb66@googlegroups.com> <297d274c-fc66-4867-9234-09deb366f222@googlegroups.com> <nvl8cd$34g$1@node2.news.atman.pl> <nvmu80$m0q$1@node2.news.atman.pl> <47df4df2-b032-45ae-9afd-07739a45a07e@googlegroups.com> NNTP-Posting-Host: 77-45-32-250.sta.asta-net.com.pl Mime-Version: 1.0 X-Trace: node1.news.atman.pl 1480097332 26895 77.45.32.250 (25 Nov 2016 18:08:52 GMT) X-Complaints-To: usenet@atman.pl NNTP-Posting-Date: Fri, 25 Nov 2016 18:08:52 +0000 (UTC) In-Reply-To: <47df4df2-b032-45ae-9afd-07739a45a07e@googlegroups.com> X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.17514 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit