<br><br><div class="gmail_quote">2009/12/21 Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net">oej@edvina.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
21 dec 2009 kl. 00.04 skrev Olivier:<br>
<div><div></div><div class="h5"><br>
> Hi,<br>
><br>
> I'm banging my head over this.<br>
><br>
> Usually, I'm using a SIP hardphone feature called "Call Pickup Starcode" to enhance BLF with Directed Call Pickup :<br>
> basically, SIP hardphone (here a Thomson ST2030S) is configured to send an INVITE message whenever a BLF is pressed while blinking.<br>
> The INVITE is build with the extension number (attached to the BLF that was blinking and pressed) prepended by a customizable Starcode sequence.<br>
><br>
> For instance, when extension 142 is ringing (and *8 is the CallPickup Starcode), pressing the associated BLF would make the hardphone send an INVITE to extension *8142.<br>
><br>
> With 1.6.1.11, this INVITE is treated as if "call picker" had dialed *8142 : it enters dialplan with appropriate extension and context.<br>
> With 1.6.2.0, this INVITE fails with message like:<br>
> chan_sip.c:19814 handle_request_invite: Trying to pick up 462@subs<br>
> The worst thing is that the INVITE message seems ignored and "Call Picker" phone keeps waiting for a reply from Asterisk.<br>
><br>
><br>
> Reading UPGRADE-1.6.txt didn't gave me any clue (as I suspected a change in call-limit, counteronpeer, ... variable in sip.conf).<br>
><br>
> Is someone successfully using Directed Pickup with 1.6.2 ?<br>
><br>
<br>
</div></div>The first paragraph under "SIP CHANGES" in CHANGES reads:<br>
" * Added support for SUBSCRIBE/NOTIFY with dialog-info based call pickups.<br>
Snom phones use this for call pickup of extensions that the phone is<br>
subscribed to.<br>
"<br>
<br>
I bet it's this code that messes with you. I am not aware of the details of the implementation, so I can't say if there's a way to turn it off.<br></blockquote><div><br>Hi Olle,<br><br>Yes, I've read this paragraph before posting and to be honest, I couldn't see any obvious relation with my issue as in my case, BLF are not fully broken : BLF are blinking, on and off as usual, and pressing a blinking BLF generates an INVITE.<br>
<br>The only change I saw, is that with 1.6.1, when Asterisk receives a BLF-generated INVITE *8142, it enters appropriate context and extension and now, with 1.6.2, it doesn't though it still accept hand-typed *8142 sequence.<br>
<br>I'll dig deeper as obviously, there must be a difference somewhere between both INVITEs (the one when typing a *8142 sequence and the one generated when pressing a blinking BLF).<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
/O<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>