[VoiceOps] The peer of my peer is my peer?

[anorexicpoodle]

Considering that, based on past conversations with my L3 SE, I believe
depending on the network you are on L3 doesn't necessarily have the
ability to trap "on network" calls as such and lets them go to PSTN and
hairpin back, I wouldn't consider this to be a big issue but it means
you will find common ground there. I think their Vector network is a bit
more intelligent, however since you never converse directly with another
customer (look at the traffic you send L3, they hold all media), I cant
imagine them not just routing this through a media server and
trans-coding between the disparate parties.

On Tue, 2010-07-13 at 15:38 -0500, Hiers, David wrote:
> Every so often this issue comes up, and I want to get a read on it
> from other VOIP resellers...
> 
>  
> 
> Consider a couple of unrelated VOIP resellers that peer with a carrier
> like L3.  Both can interop with L3 using strict SIP and RTP settings
> (max forwards, g729 only, 10ms ptime, whatever).  Both are free to
> select mutually incompatible settings.  For instance, reseller A can
> chose 729 only, and reseller B can choose 711 only.  L3 will connect
> both to the PSTN without any trouble.
> 
>  
> 
> Everything is good until they try to call each other.  Then the
> mutually incompatible settings will break calls or render predicted
> usage patterns invalid.  Sure, you’re still signaling to a L3 SIP
> server, but some the information in the SIP/SDP packets that you
> receive is controlled by the other reseller.
> 
>  
> 
> How often do you see problems related to the peer of your peer?
> 
>  
> 
>  
> 
>  
> 
>  
> 
> David Hiers
> 
> CCIE (R/S, V), CISSP
> ADP Dealer Services
> 2525 SW 1st Ave.
> Suite 300W
> Portland, OR 97201
> o: 503-205-4467
> f: 503-402-3277
> 
>  
> 
> 
> 
> ______________________________________________________________________
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and
> confidential. If the reader of the message is not the intended
> recipient or an authorized representative of the intended recipient,
> you are hereby notified that any dissemination of this communication
> is strictly prohibited. If you have received this communication in
> error, please notify us immediately by e-mail and delete the message
> and any attachments from your system.
> 
> 
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100713/78227f14/attachment-0001.html>