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. test (Hiers, David)
2. Re: test (Hiers, David)
3. Re: test (Jay Hennigan)
4. Re: test (Matt Yaklin)
5. Re: test (Feby Francis)
6. Major carriers and odd T.38 behavior (Mark R Lindsey)
7. Re: test (Shripal Daphtary)
----------------------------------------------------------------------
Message: 1
Date: Thu, 19 Sep 2013 16:51:24 +0000
From: "Hiers, David" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [VoiceOps] test
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
test
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130919/d4bb0998/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 19 Sep 2013 16:56:06 +0000
From: "Hiers, David" <[email protected]>
To: Matt Yaklin <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] test
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
Thanks!
David
-----Original Message-----
From: Matt Yaklin [mailto:[email protected]]
Sent: Thursday, September 19, 2013 09:56
To: Hiers, David (DS)
Cc: [email protected]
Subject: Re: [VoiceOps] test
I see your message.
[email protected]
On Thu, 19 Sep 2013, Hiers, David wrote:
>
> test
>
> ?
>
> ?
>
> ?
>
> 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.
>
>
>
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.
------------------------------
Message: 3
Date: Thu, 19 Sep 2013 10:07:28 -0700
From: Jay Hennigan <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] test
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
On 9/19/13 9:51 AM, Hiers, David wrote:
> test
It worked.
> 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.
By sending an e-mail to any of my addresses you are agreeing that:
* I am by definition, ?the intended recipient.?
* All information in the e-mail is mine to do with as I see fit and make
such financial profit, political mileage, or good joke as it lends
itself to.
* I may take the contents as representing the views of your company.
* This overrides any disclaimer or statement of confidentiality that may
be included on your message.
--
Jay Hennigan - CCIE #7880 - Network Engineering - [email protected]
Impulse Internet Service - http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV
------------------------------
Message: 4
Date: Thu, 19 Sep 2013 12:55:38 -0400 (EDT)
From: Matt Yaklin <[email protected]>
To: "Hiers, David" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] test
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
I see your message.
[email protected]
On Thu, 19 Sep 2013, Hiers, David wrote:
>
> test
>
> ?
>
> ?
>
> ?
>
> 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.
>
>
>
------------------------------
Message: 5
Date: Thu, 19 Sep 2013 13:33:40 -0400
From: Feby Francis <[email protected]>
To: "Hiers, David" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] test
Message-ID:
<CAEcHfMPGp=YgcK1K=cE+pgVOzf3AvvsBJTBkB64EN9iCnbL=s...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I see your test message.
Feby Francis
> ** **
>
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130919/fff9e576/attachment-0001.html>
------------------------------
Message: 6
Date: Thu, 19 Sep 2013 14:07:40 -0400
From: Mark R Lindsey <[email protected]>
To: "<[email protected]>" <[email protected]>
Subject: [VoiceOps] Major carriers and odd T.38 behavior
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I've recently bumped into some odd restrictions with the largish (nationwide,
incumbent LEC) Sonus-based SIP carriers, such as:
(a) Carrier Restriction: If g711u is the preferred codec in a call, then the
call will never be re-invited to T.38.
Implication: Any call from a line that could be connected to a fax machine
cannot be started with G.711 as the preferred codec.
(b) Carrier Restriction: The SIP carrier will never send the T.38 re-INVITE,
even if the call is going to the SIP Carrier.
Implication: I have to use SIP-POTS gateways (ATAs, IADs) that are able to
re-INVITE to T.38 when they originate the call, while many ATAs/IADs would
expect the receiving T.38 device to do the re-INVITE.
It seems like these implications limit the options available for ATAs and IADs,
and the intended use of codecs for commercial lines that may carry both voice
and fax.
Has anyone successfully worked through it all?
On Jan 10, 2012, at 1:15, Ryan Delgrosso <ryandelgrosso at gmail.com> wrote:
> I have seen numerous scenarios where a softswitch acting as a forking proxy
> will use a dummy SDP in its outgoing invite (Metaswitch and Sylantro both
> come to mind here), and immediately will re-invite when the far end has
> answered.
>
> I have also seen numerous scenarios where fax servers will send the initial
> invite with G711 and then instantly re-invite to T.38 upon answer.
>
> Dont stand on convention or BCP here, the re-invite often comes from the
> calling party, and sometimes a few times.
>
> On 01/04/2012 06:46 AM, Mark R Lindsey wrote:
>> The IETF informational draft: "SIP Support for Real-time Fax: Call Flow
>> Examples And Best Current Practices" shows the re-INVITEs from the called
>> party. This is still conventional best practice.
>>
>> http://tools.ietf.org/html/draft-ietf-sipping-realtimefax-01
>>
>>
>> Mike Coffee's talk at SIPNOC 2011 discussed the expectations, showed how
>> things can fall apart:
>>
>>
>> http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,115/Itemid,261/
>>
>>
>> -- Mark R Lindsey mark at ecg.co +1-229-316-0013 http://ecg.co/lindsey
>>
>>
>>
>>
>> On Jan 4, 2012, at 04:35 , Nathan Anderson wrote:
>>
>>> This might not be the most appropriate forum for such a question, but given
>>> that implementation bugs in either NOC gear or CPE gear can cause headaches
>>> for network operators, I offer this here in the hope that perhaps a fellow
>>> VoiceOp here may have run into this before and knows the answer...
>>>
>>> It is my understanding that with SIP, *either* party to a call can send
>>> another INVITE (a so-called "re-invite") at any time during an active
>>> session; this could be used to change the endpoint of a call or redirect it
>>> elsewhere, and is also commonly used to renegotiate the media in use
>>> (audio, video, image, and associated codecs) without dropping the call even
>>> while the endpoints remain the same.
>>>
>>> Does this hold true, though, for re-invites whose purpose is to switch from
>>> an RTP audio stream to a T.38 UDPTL stream? Can *either* peer send that
>>> INVITE? Or is there a rule -- spoken or unspoken -- that states that a
>>> T.38 re-invite can only be initiated by the *receiver* of the fax, and not
>>> the transmitter?
>>>
>>> I have some ATAs that appear to send out a T.38 re-invite upon detection of
>>> a fax tone regardless of whether the ATA placed the call or answered the
>>> call, and if I am understanding what I'm seeing in my packet captures, I
>>> think the fact that these ATAs do this even when they are going to play the
>>> role of the T.38 transmitter is confusing the heck out of my (Asterisk) SBC
>>> and the termination provider. But I can't find any concrete evidence to
>>> support the idea that T.38 re-invites should only be initiated by the
>>> receiver.
------------------------------
Message: 7
Date: Thu, 19 Sep 2013 14:08:06 -0400
From: Shripal Daphtary <[email protected]>
To: Feby Francis <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] test
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Got it. Where has everybody been?
Shripal
> On Sep 19, 2013, at 1:33 PM, Feby Francis <[email protected]> wrote:
>
> I see your test message.
>
> Feby Francis
>>
>>
>> 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
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130919/a2df181c/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
End of VoiceOps Digest, Vol 51, Issue 1
***************************************
