Re: nf_conntrack_sip problem

[Joerg Dorchain <joerg@dorchain.net>]

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On Thu, Jul 02, 2009 at 10:17:41AM +0200, Joerg Dorchain wrote:
> 
> I works, but somewhat ugly.
> # conntrack -E expect
> 180 proto=17 src=0.0.0.0 dst=85.93.219.122 sport=0 dport=11080
> 180 proto=17 src=0.0.0.0 dst=85.93.219.122 sport=0 dport=11081
> 180 proto=17 src=0.0.0.0 dst=212.88.133.153 sport=0 dport=7076
> 180 proto=17 src=0.0.0.0 dst=212.88.133.153 sport=0 dport=7077
> 
> All the places where the ip is 0.0.0.0 or the port is 0 could be
> filled more specifically. The necessary information is available
> in the same SIP/SDP flow as the used information. Besides the two
> RTP stream are unidirectional, so I'd like to have something like
> this:
> 180 proto=17 src=212.88.133.153 dst=85.93.219.122 sport=7076 dport=11080
> 180 proto=17 src=85.93.219.122 dst=212.88.133.153 sport=11081 dport=7077

Sorry for replying to often to myself, I have another addendum:
In case of asterisk reinvites in order to have to RTP stream
moved away from the machine, there are still connections expected
despite that these invites are explicitly meant to stop rtp
streams to the local machine.

Joerg

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]