Hello, I'm using Thomson/Technicolor ST2030S hardphones with Asterisk 1.6. Changing from 1.6.1.18 to 1.6.2.6, I can see a change in Pickup's behaviour and I'm a bit confused about it.
With 1.6.2.6, when extension 7791 is calling extension 7792, I can see INVITE messages coming in and out Asterisk. I can also see a NOTIFY message advertising this call to subscriber 7793, for instance. Here is an extract of this message : NOTIFY sip:[email protected]:5060;user=phone SIP/2.0 <snip> Call-ID: [email protected] <snip> Content-Length: 212 >From then, if BLF 7792 on extension 7793 is pressed, then an INVITE message is send with : INVITE sip:*[email protected]:5060;user=phone SIP/2.0 <snip> Replaces: [email protected] <snip> This Replaces header refers to RFC3891 which is not yet supported in Asterisk (see http://www.voip-info.org/wiki/view/Asterisk+SLA) This INVITE fails with : <snip> chan_sip.c: Trying to pick up 7...@subs <snip> app_directed_pickup.c: No target channel found for 7792. If I'm dialing *87792 instead of using BLF, then I'm entering the dialplan part in which there is Pickup(${EXTEN:2...@pickupmark) and the call is correctly pickup. So my understanding is : when upgrading from 1.6.1 to 1.6.2, Asterisk must somehow advertise a newly supported SIP capability which is now used by ST2030S hardphones to build Pickup requests. My question is : - is my understanding correct ? - if positive, is there a way to tame asterisk to behave appropropriately ? Regards
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
