Litchralee_v6Mar 4

I recently took up an assignment to make certain SIP phones operate on a not-too-abnormal corporate network. I figured that while SIP appliances are ancient, they would still support modern #LegacyIP things like NAT traversal, since this network has no #IPv6 and there were two layers of NAT to the SIP server. How hard could it be?

Two weeks later, I have seen things. My naivete has yielded to the confounding world of 2000s era VoIP stacks, when SIP interop was non-existent. I wish I didn't know

Show threadHugo Slabbert ⚠️Mar 4

@litchralee_v6

reads "SIP"
reads "NAT traversal

runs, hides, changes all published contact information

Show threadHugo Slabbert ⚠️Mar 5

@litchralee_v6

... two layers of NAT to the SIP server

screaming

Show threadHugo Slabbert ⚠️Mar 5
Show threadLitchralee_v6Mar 5

@hugo I too would scream, but the RTP audio stream is broken in one direction due to expiring conntrack entries after the 1 minute mark during the call, so I'm just yelling into a telephone where no one can hear me.

If we had end-to-end IPv6, p2p VoIP calls could have been glorious.

Show threadHugo Slabbert ⚠️

@litchralee_v6

I Have a Unidirectional RTP Stream, and I Must Scream.

Mar 5 at 5:38amWeb