On Nov 5, 2007 9:48 AM, Richard Neese <[EMAIL PROTECTED]> wrote: > your missing info like what ver of asterisk > > > > > > > On Monday 05 November 2007 23:36:07 Adam Vande More wrote: > > Hello, > > > > I'm receiving error's when trying to implement subscriptions on asterisk. > > Specfically on the failed to extend from x to xx parts. I can find no > > examples of dealing with this issue. The notify packet seems to be sent to > > the phone, however the content length is 0. Do anyone have insight? > > > > <--- Transmitting (no NAT) to 192.168.0.183:2057 ---> > > SIP/2.0 200 OK^M > > Via: SIP/2.0/UDP 192.168.0.183:2057;branch=z9hG4bK-nwx9atho5sws;received= > > 192.168.0.183;rport=2057^M > > From: <sip:[EMAIL PROTECTED]>;tag=8bxn28mrm9^M > > To: <sip:[EMAIL PROTECTED];user=phone>;tag=as5a9e0671^M > > Call-ID: [EMAIL PROTECTED] > > CSeq: 2 SUBSCRIBE^M > > User-Agent: Asterisk PBX SVN-trunk-r84726M^M > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY^M > > Supported: replaces^M > > Expires: 3600^M > > Contact: <sip:[EMAIL PROTECTED]>;expires=3600^M > > Content-Length: 0^M > > ^M > > > > <------------> > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 44 > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 157 > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 41 > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 49 > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 48 > > [Nov 5 12:12:52] VERBOSE[1079] logger.c: Reliably Transmitting (no NAT) to > > 192.168.0.183:2057: > > NOTIFY sip:[EMAIL PROTECTED]:2057;line=gv8x1x75 SIP/2.0^M > > Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK5266ef46;rport^M > > Max-Forwards: 70^M > > From: <sip:[EMAIL PROTECTED];user=phone>;tag=as5a9e0671^M > > To: <sip:[EMAIL PROTECTED]>;tag=8bxn28mrm9^M > > Contact: <sip:[EMAIL PROTECTED]>^M > > Call-ID: [EMAIL PROTECTED] > > CSeq: 102 NOTIFY^M > > User-Agent: Asterisk PBX SVN-trunk-r84726M^M > > Event: dialog^M > > Content-Type: application/dialog-info+xml^M > > Subscription-State: active^M > > Content-Length: 0^M > > ^M > > > > Thanks
It was in the packet header....Asterisk PBX SVN-trunk-r84726M. I'm no asterisk guru, but I think asterisk is having an issue generating the xml payload for the packet. I think that's what these notices are: [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 44 [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 157 [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 41 [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 49 [Nov 5 12:12:52] VERBOSE[1079] logger.c: failed to extend from 0 to 48 and that's why the content length is 0. -- Adam Vande More Systems Administrator Mobility Sales _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- Asterisk-BSD mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-bsd
