t_lookup_request:too few headers was [Re: [Serusers] SIP notify via sipsak, too many hops loop]

Nils Ohlmeier lists at ohlmeier.org
Fri May 20 14:04:14 CEST 2005


Your message does not have a branch value and no From tag.

  NO

On Friday 20 May 2005 13:51, Iqbal wrote:
> Hi
>
> As an update, have managed to remove the "too many hops" error, but now
> have this
>
>  ERROR: TM module: t_lookup_request: too few headers
>  3(27346) parse_headers: flags=4
>  3(27346) parse_headers: flags=-1
>  3(27346) check_via_address(a.b.c.d, sip-voip.net, 0)
>  3(27346) ERROR: sl_reply_error used: Transaction tuple incomplete (9/SL)
>  3(27346) DEBUG:destroy_avp_list: destroying list (nil)
>  3(27346) receive_msg: cleaning up
>
> not sure which headers I'm missing, or how many there should be
>
> iqbal
>
> Iqbal wrote:
> > Hi
> >
> > I am trying to send
> >
> > NOTIFY sip:040600 at sip.domain.com SIP/2.0
> > Via: SIP/2.0/UDP a.b.c.d:5060
> > From: <sip:vmserver at sip.domain.com>
> > To: <sip:040600 at sip.domain.com>
> > Contact: <sip:040600 at a.b.c.d>
> > Call-ID: 4d61cf9e505d40e905032a18329d61ec at a.b.c.d
> > CSeq: 1 NOTIFY
> > User-Agent: VoiceMail
> > Event: message-summary
> > Content-Type: application/simple-message-summary
> > Content-Length: 40
> >
> >
> > Messages-Waiting: yes
> > Voicemail: 23/2
> >
> > using
> >
> > if (src_ip == a.b.c.d) {
> >        log(1, "INSIDE ROUTE 2");
> >         if (!t_relay()) {
> >                sl_reply_error();
> >                break;
> >                };
> >        };
> >
> > in my NOTIFY route
> >
> > however I keep getting too many hops. Should sipsak send the message
> > to ser, or should it go direct to the IPphone, I am guessing at the
> > former.
> >
> > Iqbal
> >
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
> >
> > .
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers




More information about the sr-users mailing list