[Serusers] SUBSCRIBE/NOTIFY and SCS-Client; SER sends wrong To header field

Axel Böger Axel.Boeger at freenet-ag.de
Mon Apr 26 11:31:47 CEST 2004


Hi,

your fix works fine. Thanks for your help.

  Axel


> -----Original Message-----
> From: Jan Janak [mailto:jan at iptel.org]
> Sent: Sunday, April 25, 2004 10:37 PM
> To: Axel Böger
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] SUBSCRIBE/NOTIFY and SCS-Client; SER 
> sends wrong To header field
> 
> 
> Thanks for the report ! It should be fixed in the CVS. Could you,
> please, retry and let me know ?
> 
>   Jan.
> 
> On 22-04 09:53, Axel Böger wrote:
> > Hi,
> > 
> > I've tried to test the pa module (ser 0.8.12) in 
> conjunction with the
> > SCS Client.
> > The SCS Client appends a special generic param: 'ScsId=ch' at the
> > From: header in the subscribe message. And the NOTIFY answer from
> > ser contains this param but omits the semicolon. So the 
> NOTIFY message
> > will be treated as wrong.
> > 
> > The ser config for SUBSCRIBE method is straight forward:
> >   if (method=="SUBSCRIBE")
> >   {
> >     if (t_newtran())
> >     {
> >       handle_subscription("registrar");
> >     };
> >   }; # subscribe
> > 
> > The ngrep output for this transaction is:
> > #
> > U 195.4.20.71:5060 -> 194.97.99.50:5060
> >   SUBSCRIBE sip:snom at fn-sip.mcbone.net SIP/2.0..Via: 
> SIP/2.0/UDP 195.4.20.71.
> >   .To: sip:snom at fn-sip.mcbone.net..From:  
> <sip:aboeger at fn-sip.mcbone.net>;tag
> >   =11b78ed1b717552;ScsId=ch..Call-ID: 
> dc8b5b893e68391d9b2dfc807f8e3ba2..CSeq:
> >    1325665313 SUBSCRIBE..Max-Forwards: 70..Contact: 
> sip:195.4.20.71..Event: p
> >   resence..Expires: 3600..Content-Length: 0..User-Agent: 
> SCS/v3.1.12.33....
> > #
> > U 194.97.99.50:5060 -> 195.4.20.71:5060
> >   SIP/2.0 200 OK..Via: SIP/2.0/UDP 195.4.20.71..To: 
> sip:snom at fn-sip.mcbone.ne
> >   t;tag=91083b2aa33cb6d5c9260125dc95d5f0-efd4..From:  
> <sip:aboeger at fn-sip.mcb
> >   one.net>;tag=11b78ed1b717552;ScsId=ch..Call-ID: 
> dc8b5b893e68391d9b2dfc807f8
> >   e3ba2..CSeq: 1325665313 SUBSCRIBE..Server: Sip EXpress 
> router (0.8.12a (i38
> >   6/linux))..Content-Length: 0..Warning: 392 
> 194.97.99.50:5060 "Noisy feedbac
> >   k tells:  pid=26439 req_src_ip=195.4.20.71 
> req_src_port=5060 in_uri=sip:sno
> >   m at fn-sip.mcbone.net out_uri=sip:snom at fn-sip.mcbone.net 
> via_cnt==1"....
> > #
> > U 194.97.99.50:5060 -> 195.4.20.71:5060
> >   NOTIFY sip:195.4.20.71 SIP/2.0..Via: SIP/2.0/UDP 
> 194.97.99.50;branch=z9hG4b
> >   K6d55.e01a2e91.0..To: 
> <sip:aboeger at fn-sip.mcbone.net>ScsId=ch;tag=11b78ed1b
> >   717552..From: 
> sip:snom at fn-sip.mcbone.net;tag=91083b2aa33cb6d5c9260125dc95d5
> >   f0-efd4..CSeq: 1 NOTIFY..Call-ID: 
> dc8b5b893e68391d9b2dfc807f8e3ba2..Content
> >   -Length: 302..User-Agent: Sip EXpress router(0.8.12a 
> (i386/linux))..Event:
> >   presence..Content-Type: 
> application/xpidf+xml..Subscription-State: active;e
> >   xpires=3600....<?xml version="1.0"?>..<!DOCTYPE presence 
> PUBLIC "//IETF//DT
> >   D RFCxxxx XPIDF 1.0//EN" 
> "xpidf.dtd">..<presence>..<presentity uri="sip:sno
> >   m at fn-sip.mcbone.net;method=SUBSCRIBE"/>..<atom 
> id="9r28r49">..<address uri=
> >   "sip:snom at fn-sip.mcbone.net">..<status 
> status="closed"/>..</address>..</ato
> >   m>..</presence>..
> > #
> > U 195.4.20.71:5060 -> 194.97.99.50:5060
> >   SIP/2.0 400 Syntax Error..Call-ID: 
> dc8b5b893e68391d9b2dfc807f8e3ba2..CSeq:
> >   1 NOTIFY..From: 
> sip:snom at fn-sip.mcbone.net;tag=91083b2aa33cb6d5c9260125dc95
> >   d5f0-efd4..Via: SIP/2.0/UDP 
> 194.97.99.50;branch=z9hG4bK6d55.e01a2e91.0..Con
> >   tent-Length: 136..Content-Type: text/plain....While 
> parsing "To": header ex
> >   pected CRLF.. Missing or invalid To header.. Missing or 
> invalid To header..
> >    Missing or invalid To header..
> > #
> > 
> > For me it seems to be an error in ser. Have anyone an idea 
> for a workaround?
> > 
> >   Regards,
> >     Axel
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
> 




More information about the sr-users mailing list