Convert barant.com JET 1.4 marketing pages to jetc/.jtc (local, non-production)

Pulls .page files and shared template infrastructure (mainpagetemplate.temp,
menu.bar, barant.tag, opensource.menu, cart.menu, login.menu) read-only from
barant.com via SFTP into jetc/barant-site/src, then convert.py mechanically
flattens them into self-contained .jet files: linkbutton becomes a plain
anchor link (the old SESSIONCTL PAGE/PROCESS form-postback model has no
equivalent here - each page is its own real #api route now, not a shared
single-form state machine), sectionframe is expanded per its barant.tag
definition, /images/* references are fetched and inlined as data URIs
(APIServer has no static-file serving), and session-gated chrome (cart,
account/admin, login.menu) is resolved to its anonymous-visitor default
state, since no session/DB backend is wired into this conversion.

17 pages convert and serve cleanly end-to-end (verified via a local
apiserver-barant-site.json instance on :8081, kept separate from the
existing demo server on :8080 to avoid a /main route collision with the
earlier hand-cloned barant.jet). Two pages deliberately out of scope for
this pass: davidarant.page (whiledir filesystem iteration) and the
per-topic sub-pages of jet.page (dispatches on an ARGS query param this
conversion does not populate - only the default overview state converts).
vst.page/modular1.page/modular1_patches.page also deferred - they pull
live product rows via sql, a real backend dependency beyond "pages and
their template" scope.

Nothing was written back to barant.com - SFTP access was read-only
throughout, per explicit instruction to convert locally without touching
the original site.

jetc/barant-site/src/siptrunk.page

@@ -0,0 +1,50 @@
+<page template="mainpagetemplate">
+<title>SIP Trunking</title>
+<style>
+.price {display: table-cell;
+        background-color: #fff; 
+        width: 100px;
+	height: 100px; 
+	text-align: center;
+	vertical-align: middle;
+	border: 1px solid #000;
+	border-radius: 20px;
+       }
+.number {font-size: 30px;}
+</style>
+<contents>
+<sectionframe title="SIP Trunking">
+<h1>For PBX Systems</h1>
+<p>Some of the best prices around for adding trunks to your PBX. We
+have 10, 25 and 50 channel plans to ensure your calls get through.</p>
+<p>Our flat rate plans don't charge you for minutes for either inbound
+or outbound.</p>
+<div style="display: table; border-spacing: 10px;">
+<div class="price"><div class="number">3</div>Lines<br><br>$25/month</div>
+<div class="price"><div class="number">10</div>Lines<br><br>$50/month</div>
+<div class="price"><div class="number">25</div>Lines<br><br>$100/month</div>
+<div class="price"><div class="number">50</div>Lines<br><br>$175/month</div>
+<div class="price"><div class="number">100</div>Lines<br><br>$300/month</div>
+</div>
+<p>Please feel free to call for other options and pricing.</p>
+<p>Our SIP trunks work with any PBX that has an internet connection.</p>
+<p>We require high speed internet connections to provide the higher
+number of lines. Special routers that provide a QoS VoIP functionality
+should be employed for serious usage to improve quality. The faster
+the better. We do not provide equipment but can recommend routers that
+we know work well with VoIP.</p>
+<p>We do not support robo-dialer abuse for outbound dialing systems so
+please do not ask for pricing or purchase our services if you intend to
+use these devices on our networks.</p>
+<h1>Don't have a PBX and dont't want one?</h1>
+If your organization does not have or need a PBX but wish to have a
+phone for 1 or 2 lines then you can just ask for our individual phone
+service for any VoIP phone or VoIP converter for any old standard
+phone line. Please contact us for more information.  
+<h1>Don't have a PBX but want one?</h1>
+We can also host a PBX for you as well. Complete functionality
+utilizing FreePBX can be provided on the internet so you do not need
+to worry about the hardware. We manage and maintain everything for you.
+</sectionframe>
+</contents>
+</page>