Verizon Wireless LTE/4G and SIP Header Manipulation
Hi All, Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this. Thanks Mark
On Tue, Sep 22, 2015 at 12:03 PM, Mark Stevens <manager@monmouth.com> wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this.
I'm shocked that the cellular carrier is making over-the-top phone calls non-functional. I'm sure they'll agree to meet you at their CO so you can do the proper work request sometime between 6am and 7pm in 2 weeks time. go incombancy!
Thanks
Mark
On Tue, Sep 22, 2015 at 12:22 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
On Tue, Sep 22, 2015 at 12:03 PM, Mark Stevens <manager@monmouth.com> wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this.
I'm shocked that the cellular carrier is making over-the-top phone calls non-functional. I'm sure they'll agree to meet you at their CO so you can do the proper work request sometime between 6am and 7pm in 2 weeks time.
joking aside, are you sure the packets get mangledin VZW and not elsewhere along the path? how would you be able to prove it?
go incombancy!
Thanks
Mark
I've seen this behavior before (a few years back). Moved off of VzW for this reason (i'm lazy to implement workarounds). IIRC when i investigated, the ALG was trying to not do something nefarious but just poorly implemented. On Tue, Sep 22, 2015 at 12:51 PM, Christopher Morrow < morrowc.lists@gmail.com> wrote:
On Tue, Sep 22, 2015 at 12:22 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
On Tue, Sep 22, 2015 at 12:03 PM, Mark Stevens <manager@monmouth.com> wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this.
I'm shocked that the cellular carrier is making over-the-top phone calls non-functional. I'm sure they'll agree to meet you at their CO so you can do the proper work request sometime between 6am and 7pm in 2 weeks time.
joking aside, are you sure the packets get mangledin VZW and not elsewhere along the path? how would you be able to prove it?
go incombancy!
Thanks
Mark
-- William McCall
The TAG unique identifier is being changed and this only happens through VZ LTE networks, not wired networks or even other cellular data networks (Sprint, ATT, T-Mobile) Their phones are IPV6 so the packets are getting converted to IPV4 so it is either happening there or there is a global ALG in Verizon land that is doing it . For positive proof I would need Verizon to fess up (LOL) but that will not happen or sniff traffic from the cellphone itself. On 9/22/2015 3:51 PM, Christopher Morrow wrote:
On Tue, Sep 22, 2015 at 12:22 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
On Tue, Sep 22, 2015 at 12:03 PM, Mark Stevens <manager@monmouth.com> wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this.
I'm shocked that the cellular carrier is making over-the-top phone calls non-functional. I'm sure they'll agree to meet you at their CO so you can do the proper work request sometime between 6am and 7pm in 2 weeks time.
joking aside, are you sure the packets get mangledin VZW and not elsewhere along the path? how would you be able to prove it?
go incombancy!
Thanks
Mark
On Tue, Sep 22, 2015 at 4:16 PM, Mark Stevens <manager@monmouth.com> wrote:
The TAG unique identifier is being changed and this only happens through VZ LTE networks, not wired networks or even other cellular data networks (Sprint, ATT, T-Mobile) Their phones are IPV6 so the packets are getting converted to IPV4 so it is either happening there or there is a global ALG in Verizon land that is doing it . For positive proof I would need Verizon to fess up (LOL) but that will not happen or sniff traffic from the cellphone itself.
welp, interesting, good luck in your battle with the pstn.
On Sep 22, 2015, at 4:24 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
On Tue, Sep 22, 2015 at 4:16 PM, Mark Stevens <manager@monmouth.com> wrote:
The TAG unique identifier is being changed and this only happens through VZ LTE networks, not wired networks or even other cellular data networks (Sprint, ATT, T-Mobile) Their phones are IPV6 so the packets are getting converted to IPV4 so it is either happening there or there is a global ALG in Verizon land that is doing it . For positive proof I would need Verizon to fess up (LOL) but that will not happen or sniff traffic from the cellphone itself.
welp, interesting, good luck in your battle with the pstn.
I’ll say it’s not just VZW that does this, there are issues with many CPE devices that mangle SIP traffic due to broken ALG. My plea is if you’re a carrier that provides a CPE, *please* provide an option to disable the ALG, or expose it to the customer so they can disable it. *Looks in 7018/7132 direction* - Jared
On 9/22/15 9:03 AM, Mark Stevens wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this.
sounds like a really good application for TLS
Thanks
Mark
TLS would be perfect but it is not viable at this point. I guess with Verizon being what they are, it is time to start working on a SIP over TLS implementation. On 9/22/2015 12:24 PM, joel jaeggli wrote:
On 9/22/15 9:03 AM, Mark Stevens wrote:
Hi All,
Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this. sounds like a really good application for TLS
Thanks
Mark
Send all of your signaling over TLS and they won't be able to see or modify it. Steven Naslund Chicago IL -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Mark Stevens Sent: Tuesday, September 22, 2015 11:03 AM To: nanog@nanog.org Subject: Verizon Wireless LTE/4G and SIP Header Manipulation Hi All, Has anyone seen that something (most likely an alg) on Verizon's LTE/4G network is rewriting SIP headers,in particular From Tag identifiers? We cannot make a SIP call from our cellphones (using cellular data) beyond 30 seconds because the TAGs are rewritten and the destination Asterisk server drops the call because of this. Thanks Mark
participants (6)
-
Christopher Morrow -
Jared Mauch -
joel jaeggli -
Mark Stevens -
Naslund, Steve -
William McCall