Send VoiceOps mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."


Today's Topics:

   1. GRE (Bob Hancock)


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

Message: 1
Date: Tue, 13 Aug 2013 09:17:52 -0500
From: Bob Hancock <[email protected]>
To: [email protected]
Subject: [VoiceOps] GRE
Message-ID:
        <CAMZUC4hSyoG6FrUnBfQz-MVN7oKHsi_a-OPUdyhJ+H6N=t_...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I have a project in which a user is interesting in interconnecting and
deploying ATAs for VoIP services but wants to use private IP addressing on
the devices. My initial though is to NAT these devices and allow my SBC to
handle NAT traversal for them. This allows the to use their dedicated
connection to my network or if that link goes down fail over to moving to
connecting across the internet. They are interested in potentially doing a
GRE tunnel and keeping the private addressing in place as it traverses that
tunnel. I am concerned about encapsulating the VoIP traffic as well as with
the fail over options. Does anybody have any experiences with VoIP over GRE
tunnels and what type of results and challenges you encountered? Thanks.

--BH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/voiceops/attachments/20130813/8ae09d62/attachment-0001.html>

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

Subject: Digest Footer

_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops


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

End of VoiceOps Digest, Vol 50, Issue 5
***************************************

Reply via email to