Just what's in the wiki as far as I know.

Mike

On Wed, Dec 28, 2011 at 6:59 AM, Spiny Tel <[email protected]> wrote:

> *Also,  with Karoo Bridge
>
> 1. You could be registered with many itsp's and/or accounts at the same
> time.
> 2.  Code relatively simple javascript exit scripts for creating
> endless routing possibilities.
>
> Please, refer to sample scripts found on SIPX wiki site.
>
> Thanks *
> *
> *
> So, how can i use karoo bridge separately? Where is the source code or
> binary? Is there any documentation how to use this?
>
> Thanks
>
>
> On Fri, Dec 23, 2011 at 4:58 PM, Michael Picher <[email protected]> wrote:
>
>> Todd's dragging me in here so I'll explain virtual gateways...
>>
>> I use, what i call virtual gateways, for many reasons....  here's what
>> they are and why I use them.
>>
>> First, a virtual gateway is a gateway that is just another way to address
>> another physical gateway.  So, for instance I might have:
>>
>> *Gateway*                   * IP Address *                           *
>> Description*
>> ACodes1                   192.168.10.10
>> Audiocodes M1000 PRI GW
>> Boston911                 bos911.sip.domain                  A Record
>> configured in DNS to point to 192.168.10.10
>> Miami911                   mia911.sip.domain                  A Record
>> configured in DNS to point to 192.168.10.10
>>
>> If I were to just use the IP address for all three of the above gateways
>> and XML that is created for the dial plan would get confused.  But instead
>> by using DNS names the system will actually use them properly in the XML.
>>
>> So this is useful because we can use gateways for force outbound
>> caller-id (as well as other things).  I use this sort of configuration a
>> lot when working with emergency dialing (hence the reference to 911 above).
>>  So, out of a single gateway, I can push whatever caller-id I want
>> (assuming that the silly provider doesn't over-write that with the BTN
>> (billing telephone number)).
>>
>> Mike
>>
>> On Fri, Dec 23, 2011 at 1:03 AM, Todd Hodgen <[email protected]>wrote:
>>
>>> This can be done.   Let me provide an example.  Three companies running
>>> on
>>> one sipXecs.   Each have their own account with Broadvox.  Each Broadvox
>>> account needs to be setup to different IP addresses on their network.
>>> With
>>> this you have three different sip trunk gateways.  Set the gateway to
>>> not be
>>> for all, and assign them a branch.  Set a group of phones in that branch
>>> and
>>> they can call on that gateway.
>>>
>>> You can throw in a 4th gateway for International LD, and assign it to all
>>> three of those groups. Or one of them.  This of course is just one
>>> example.
>>> I've seen Picher talk about setting up virtual gateways as well - I
>>> suspect
>>> that would give you some other methods of doing the same.
>>>
>>> Definitely, it seems that what you are trying to do can be done, with
>>> sipxbridge.   I am assuming with Karoo as well.
>>>
>>> -----Original Message-----
>>> From: [email protected]
>>> [mailto:[email protected]] On Behalf Of Roman
>>> Gelfand
>>> Sent: Thursday, December 22, 2011 6:38 PM
>>> To: Discussion list for users of sipXecs software
>>> Subject: Re: [sipx-users] SipXecs and Karoo Bridge
>>>
>>> It has been a long time since I configured sipxbridge, but from what I
>>> could
>>> remember, if I am not mistaken, I couldn't create multiple sip trunk
>>> gateways and I couldn't associate multiple extensions with multiple itsp
>>> accounts for outgoing calls.  In the least, I couldn't dynamically change
>>> caller id.  I you could do this, I would be interested to know.
>>>
>>> BTW...
>>>
>>> In this scenario sipxbridge would not work.   If SIPX is located in
>>> dmz, ua's from internal network can not communicate with dmz network or
>>> even
>>> wan local users.  With Karoo it works.
>>>
>>> On Thu, Dec 22, 2011 at 8:20 PM, Joegen Baclor <[email protected]>
>>> wrote:
>>> > inline ...
>>> >
>>> > On 12/23/2011 02:02 AM, Sergio Torosyan wrote:
>>> >> Hello,
>>> >> Very confusing reply: Does (1) mean we can have only one ITSP on
>>> SIPxecs?
>>> >
>>> > If you are really familiar with sipX, I think you would easily
>>> > discover that sipX allows you to define multiple managed gateways.  It
>>> > is therefore imperative that sipX can support multiple itsp
>>> > registrations.   What makes Karoo Bridge different if you do opt to
>>> > use it instead of the internal sipXbridge, that it gives you a better
>>> > handle on the SIP messages that goes in an out of the ITSP.   For
>>> > example, there is an issue most recently that an ITSP sends a
>>> > max-forwards of 10 which gets depleted when the proxy and registrar
>>> > started to play ping-pong routing.   This is something that karoo
>>> > allows you to modify at will because it uses a scripting language to
>>> > allow you to manipulate sip messages.  Another easy thing to do which
>>> > are usually one liner in Karoo scripts is caller alias manipulation.
>>> >
>>> >
>>> >
>>> >>   Is
>>> >> the Karoo a bridge/SBC or it is a SIP proxy/registrar server?
>>> >
>>> >
>>> > Its a B2BUA and therefore ain't a proxy.  It's an SBC.
>>> >
>>> >
>>> >>
>>> >> Thanks,
>>> >> Sergio T.
>>> >>
>>> >>
>>> >> -----Original Message-----
>>> >> From: [email protected]
>>> >> [mailto:[email protected]] On Behalf Of Roman
>>> >> Gelfand
>>> >> Sent: Thursday, December 22, 2011 7:32 AM
>>> >> To: Discussion list for users of sipXecs software
>>> >> Subject: Re: [sipx-users] SipXecs and Karoo Bridge
>>> >>
>>> >> Also,  with Karoo Bridge
>>> >>
>>> >> 1. You could be registered with many itsp's and/or accounts at the
>>> >> same time.
>>> >> 2.  Code relatively simple javascript exit scripts for creating
>>> >> endless routing possibilities.
>>> >>
>>> >> Please, refer to sample scripts found on SIPX wiki site.
>>> >>
>>> >> Thanks
>>> >>
>>> >> On Tue, Dec 20, 2011 at 8:40 AM, Tony Graziano
>>> >> <[email protected]>  wrote:
>>> >>> sipxecs is a complete solution a box for an enterprise 9manages
>>> >>> phones, registrations, call details records, etc.), it also has
>>> >>> unified messaging components. Part of what sipxecs has is a
>>> >>> component designed to be a "mini-SBC" specifically for use with
>>> sipxecs
>>> only.
>>> >>>
>>> >>> Karoo Bridge is a Linux based SBC, and when deployed with sipxecs
>>> >>> can supplement of replace the function provided by sipxbridge only.
>>> >>> It can
>>> >> also
>>> >>> be used with many other proxies and systems. It's a SBC.
>>> >>>
>>> >>>
>>> >>> On Tue, Dec 20, 2011 at 8:02 AM, spinytel<[email protected]>
>>>  wrote:
>>> >>>>
>>> >>>> Content-Type: text/plain;
>>> >>>>   charset="utf-8"
>>> >>>> Content-Transfer-Encoding: 8bit
>>> >>>> Organization: SipXecs Forum
>>> >>>> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8<64992>
>>> >>>> Message-ID:<[email protected]>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>> Dear,
>>> >>>>
>>> >>>> Can anyone please tell me what is the difference between SipXecs
>>> >>>> and Karoo Bridge. And also what is the relation between them?
>>> >>>>
>>> >>>> I need  a proxy/bridge which can bypass/relay SIP and RTP traffic
>>> >>>> to specific Registrar/Switch. Communication between SIP Client and
>>> >>>> Bridge/Proxy will be encrypted (SIP and RTP both).
>>> >>>>
>>> >>>> Looks like karoo bridge will be my solution. Can anyone please help
>>> >>>> me on this?
>>> >>>>
>>> >>>> Thanks
>>> >>>> _______________________________________________
>>> >>>> sipx-users mailing list
>>> >>>> [email protected]
>>> >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> ======================
>>> >>> Tony Graziano, Manager
>>> >>> Telephone: 434.984.8430
>>> >>> sip: [email protected]
>>> >>> Fax: 434.465.6833
>>> >>>
>>> >>> Email: [email protected]
>>> >>>
>>> >>> LAN/Telephony/Security and Control Systems Helpdesk:
>>> >>> Telephone: 434.984.8426
>>> >>> sip: [email protected]
>>> >>>
>>> >>> Helpdesk Customers: http://myhelp.myitdepartment.net
>>> >>> Blog: http://blog.myitdepartment.net
>>> >>>
>>> >>> Linked-In Profile:
>>> >>>   http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
>>> >>> Ask about our Internet Fax services!
>>> >>>
>>> >>> _______________________________________________
>>> >>> sipx-users mailing list
>>> >>> [email protected]
>>> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> >> _______________________________________________
>>> >> sipx-users mailing list
>>> >> [email protected]
>>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> >>
>>> >> _______________________________________________
>>> >> sipx-users mailing list
>>> >> [email protected]
>>> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> >>
>>> >
>>> > _______________________________________________
>>> > sipx-users mailing list
>>> > [email protected]
>>> > List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>>
>> --
>> Michael Picher, Director of Technical Services
>> eZuce, Inc.
>>
>> 300 Brickstone Square****
>>
>> Suite 201****
>>
>> Andover, MA. 01810
>> O.978-296-1005 X2015
>> M.207-956-0262
>> @mpicher <http://twitter.com/mpicher>
>> www.ezuce.com
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>



-- 
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to