Food for thought. I think there's a reasonable argument that the whole magic of the PSTN is the interoperability it's had for decades. This interoperability comes from each switch connecting to it cleaning up whatever messes have been created in userland before handing off a clean signal and audio stream to the rest of the PSTN. I think perhaps model that doesn't does this is a model designed for the Internet, not the PSTN.
-jbn On Tue, Apr 15, 2014 at 10:25 AM, Hiers, David <[email protected]> wrote: > In our 3PCC model, the switch is not in a position to do that. It does not > control the details of the RTP stream (codec, timestamp, sequence, marker, > etc). > > > > David > > > > From: Paul Timmins [mailto:[email protected]] > Sent: Tuesday, April 15, 2014 08:20 > To: Hiers, David (DS) > Cc: [email protected] > Subject: Re: [VoiceOps] Signaling hold to the PSTN > > > > Shouldn't the local switch just play hold music into the network, and the > other side be completely unaware of hold at all? > > On Tue, 04/15/2014 10:39 AM, "Hiers, David" <[email protected]> wrote: > > Hi, > > What has been your experience in signaling holds to the PSTN? The more > everyone converts to SIP and peers with our carriers, the more stacks we see > on the far end. A growing number seem to have trouble accepting any kind of > hold SDP signals such as a=inactive/sendonly, quad zeros, etc. > > > > Is this vexing you too, or is it just me? > > > > > > > > > > > > David > > > > > > ________________________________ > > 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 > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > > ________________________________ > > 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 > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops > _______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
