[VoiceOps] Blind Transfer Issue to iPhones on Verizon

[Carlos Alvarez]

I think the issue with T-Mobile CNAM taught me that everything that goes
out to "the PSTN" needs to be sanitized.  Don't leak anything internal.  I
certainly took it for granted that if the traditional network can't pass
it, I don't need to think about it.  But now that it's headed to all being
SIP...

On Tue, Jun 6, 2017 at 9:18 AM, CCI Michael Palmer <
mpalmer at comediacommunications.com> wrote:

> David,
> I had the same issues last week, running asterisk, had a cell phone as an
> alternate destination for a ring group, passing alert info, call would not
> complete, and Level3 would return invalid SIP value sent (or something of
> the sort), and I noticed we were sending the Alert info. We ended up taking
> the alert info off the ring group and it worked. I think long term plan,
> we'll strip the alert-info off on our SBC.
>
> Michael
>
> ------------------------------
> *From: *"David Wessell" <david at ringfree.com>
> *To: *"Carlos Alvarez" <caalvarez at gmail.com>
> *Cc: *"VoiceOps (voiceops at voiceops.org)" <voiceops at voiceops.org>
> *Sent: *Monday, June 5, 2017 3:25:15 PM
> *Subject: *Re: [VoiceOps] Blind Transfer Issue to iPhones on Verizon
>
> We are running asterisk 1.8.x behind a Sansay SBC.
> We have tested iphones on other carriers and they work fine. We have
> tested other Android phones on Verizon. They work fine.
>
> The only failures are iPhones on Verizons network. We've tested
> termination both through Level3 and Bandwidth and have had the same
> duplicatable results.
>
> What we found was causing the issue was the insertion of Alert Info: into
> the SIP header. Asterisk lets us do this to define ring tones. If we remove
> that it goes away.
>
> What's odd is that this never caused an issue until this past Thursday.
>
> Thanks
> David
>
>
>
> On Mon, Jun 5, 2017 at 3:10 PM, Carlos Alvarez <caalvarez at gmail.com>
> wrote:
>
>> I haven't had any complaints like this, and I know we have quite a few
>> Verizon users.  You implied something I want to ask specifically...
>>
>> Have you actually tested blind transfers to iPhones on other carriers?
>>
>> Have you actually tested blind transfers to other phones on Verizon?
>>
>> Who is your upstream?  Many of them are doing private interconnects with
>> the cell carriers now and when that happens signaling may change or be
>> handled differently.  The substitution of the CLID and/or the call leg may
>> be the culprit here.
>>
>>
>> On Mon, Jun 5, 2017 at 8:35 AM, David Wessell <david at ringfree.com> wrote:
>>
>>> Hi All,
>>> We're seeing an issue since 6/1/17 where blind transfers from an
>>> external number to iPhones on Verizon Wireless don't ring the iPhone. Has
>>> anyone else seen this?
>>>
>>> Scenario:
>>> External caller dials in. Blind transfer is done to the Verizon iPhone.
>>> The iPhone never rings.
>>> External caller dials in. Warm transfer is done to the Verizon iPhone.
>>> The iPhone rings.
>>> Internal caller dials the Verizon iPhone and the iPhone rings.
>>>
>>> We've never seen this issue until 6/1/17. Has anyone else had complaints?
>>>
>>> Thanks
>>> David
>>>
>>> --
>>> David Wessell
>>> *Co-Owner*, Ringfree Communications, Inc.
>>> [image: Ringfree Communications Logo] <http://www.ringfree.com/>
>>> Phone:  (828) 575-0030 x101 <82825750030>
>>> Email:  david at ringfree.com
>>> Website:  www.ringfree.com
>>> 824 Locust St. Suite 200
>>> Hendersonville, NC 28792
>>> [image: Twitter] <https://www.twitter.com/RingfreeCom> [image: Facebook]
>>> <http://www.facebook.com/Ringfree> [image: LinkedIn]
>>> <http://www.linkedin.com/company/ringfree-communications-llc>
>>> How was your experience?
>>> Tell us by taking our Customer Service Survey
>>> <https://www.supersimplesurvey.com/Survey/16842/signature/>.
>>> *Confidentiality Note: * This e-mail and any attachments are
>>> confidential and may be protected by legal privilege. If you are not the
>>> intended recipient, be aware that any disclosure, copying, distribution or
>>> use of this e-mail or any attachment is prohibited. If you have received
>>> this e-mail in error, please notify us immediately by returning it to the
>>> sender and delete this copy from your system. Thank you for your
>>> cooperation.
>>>
>>> _______________________________________________
>>> VoiceOps mailing list
>>> VoiceOps at voiceops.org
>>> https://puck.nether.net/mailman/listinfo/voiceops
>>>
>>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
>
> --
> David Wessell
> *Co-Owner*, Ringfree Communications, Inc.
> [image: Ringfree Communications Logo] <http://www.ringfree.com/>
> Phone:  (828) 575-0030 x101 <82825750030>
> Email:  david at ringfree.com
> Website:  www.ringfree.com
> 824 Locust St. Suite 200
> Hendersonville, NC 28792
> [image: Twitter] <https://www.twitter.com/RingfreeCom> [image: Facebook]
> <http://www.facebook.com/Ringfree> [image: LinkedIn]
> <http://www.linkedin.com/company/ringfree-communications-llc>
> How was your experience?
> Tell us by taking our Customer Service Survey
> <https://www.supersimplesurvey.com/Survey/16842/signature/>.
> *Confidentiality Note: * This e-mail and any attachments are confidential
> and may be protected by legal privilege. If you are not the intended
> recipient, be aware that any disclosure, copying, distribution or use of
> this e-mail or any attachment is prohibited. If you have received this
> e-mail in error, please notify us immediately by returning it to the sender
> and delete this copy from your system. Thank you for your cooperation.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> 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/20170606/a3d51216/attachment-0001.html>