[cisco-voip] SIP Trunks to provider

[Lelio Fulgenzi]

In my initial talks with one provider here, we were a little dissappointed. First of all, they weren't able to offer any hard fast facts. It was all "soon to be available". Second of all, they would only allow a percentage of the network connection to be consumed by VOIP traffic. So if I wanted a 15MB SIP connection I would need to order a 30MB data connection to meet a 50% rule. 

Quite honestly, I don't think SIP there just yet. We have plans to replace our PRI equipment but I think we will continue using 6608s until SIP is ready. If we find that it's still not ready, then we can buy some PRI ports for our 3845s (if they are in place).

Lelio
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
...seen on a Geek Squad patch cord: "While it is the same length, this 7' crossover cable
is not regulation issue for most competitive Manhattan double dutch leagues.
  ----- Original Message ----- 
  From: Scott Voll 
  To: cisco-voip at puck.nether.net 
  Sent: Tuesday, June 10, 2008 11:06 AM
  Subject: [cisco-voip] SIP Trunks to provider


  I'm just getting my feet wet with SIP Trunks.  I hear lots of talk about SBC and setting up SIP Trunks to your providers.  

  my question is, are others seeing that it's ~ 34% more per channel for SIP then a conventional PRI?  If so, why are people in such a hurry to go to a SIP Trunk and spend the money on a SBC?

  Thanks for the insight

  Scott


------------------------------------------------------------------------------


  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080610/2933708f/attachment.html>