[Serusers] Via: SIP/2.0/UDP X.X.X.X; branch=0

[Klaus Darilion]

looks like the message is looped. you can verify this by sniffing on the 
loopback device too:

ngrep -d any
tcpdump -i any

if looping is the case, you have a bug in your ser.cfg

regards
klaus

Carlos Loarca wrote:
> Hi everyone:
> I have a very strange ser's behavior, I have setup my
> ser server, it works very well but when I hang up a
> call, then I recieve many messages like those below.
> 
> Max-Forwards: 59
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP 83.140.44.243;branch=0
> Via: SIP/2.0/UDP
> 213.132.115.200:5060;branch=z9hG4bK2213168
> 
> 0(15486) DEBUG : sl_filter_ACK: to late to be a local
> ACK!
>  0(15486) DEBUG:maxfwd:is_maxfwd_present: value = 59
>  0(15486) parse_headers: flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) parse_headers: this is the second via
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> = <0>;
> state=16
>  0(15486) end of header reached, state=5
>  0(15486) parse_headers: Via found, flags=200
>  0(15486) Found param type 232, <branch> =
> <z9hG4bK2213168>; state=16
> 
> The problem here is that sometimes it doesnt stop
> sending these messages until it finds the branch ID.
> What is the reason of this Via Branch=0???
> 
> I appreciate any comment about it,
> Cheers,
> /Carlos
> 
> 
> 
> CUANDO UNO SABE A DONDE VA, EL MUNDO SE ABRE PARA DEJARLO PASAR.
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers