[VoiceOps] The peer of my peer is my peer?
kristian.kielhofner at gmail.com
Tue Jul 13 17:35:47 EDT 2010
I've seen this happen with resellers that only use a proxy between
their customers (Bandwidth.com). In that case all transport, codec,
and caller ID parameters must be compatible (Bandwidth won't do
anything about them).
With Level(3) Vector they hold media and can make codecs compatible.
However, one problem we have found is Caller ID presentation. When
going to a peer Level(3) will not do a dip and set the from name, they
depend on the originating network to set the CID appropriately or they
depend on the terminating network to do a dip.
We experienced problems with this once Comcast starting using Level(3)
vector. CID name presentation would be inconsistent on calls to
On Tue, Jul 13, 2010 at 4:38 PM, Hiers, David <David_Hiers at adp.com> 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
More information about the VoiceOps