Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-31 Thread Olle E. Johansson
On 30 Mar 2015, at 16:54, Mark Michelson mmichel...@digium.com wrote: On 03/28/2015 08:06 PM, Joshua Colp wrote: George Joseph wrote: The fact that it goes to unavailable would be a bug. Why does it do so? Mark should probably chime in here but I think it's because the earliest you could

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-31 Thread Mark Michelson
On 03/31/2015 01:51 AM, Olle E. Johansson wrote: On 30 Mar 2015, at 16:54, Mark Michelson mmichel...@digium.com wrote: On 03/28/2015 08:06 PM, Joshua Colp wrote: George Joseph wrote: The fact that it goes to unavailable would be a bug. Why does it do so? Mark should probably chime in here

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-30 Thread Mark Michelson
On 03/28/2015 08:06 PM, Joshua Colp wrote: George Joseph wrote: The fact that it goes to unavailable would be a bug. Why does it do so? Mark should probably chime in here but I think it's because the earliest you could get a response from pjsip when a contact isn't reachable is the

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-30 Thread George Joseph
On Mon, Mar 30, 2015 at 8:54 AM, Mark Michelson mmichel...@digium.com wrote: On 03/28/2015 08:06 PM, Joshua Colp wrote: George Joseph wrote: The fact that it goes to unavailable would be a bug. Why does it do so? Mark should probably chime in here but I think it's because the earliest

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread Joshua Colp
George Joseph wrote: The fact that it goes to unavailable would be a bug. Why does it do so? Mark should probably chime in here but I think it's because the earliest you could get a response from pjsip when a contact isn't reachable is the unconfigurable 32 seconds. As I said that's a long

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread Joshua Colp
snip all the things G, it requires an rdata. I'll ponder further. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com www.asterisk.org --

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread Joshua Colp
George Joseph wrote: I've been trying to figure out how to get more control of the pjsip_options qualify process. Specifically, how to get a timely positive indication of failure and how to generate events on a status change. Right now when a contact is qualified, it's immediately marked as

[asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread George Joseph
I've been trying to figure out how to get more control of the pjsip_options qualify process. Specifically, how to get a timely positive indication of failure and how to generate events on a status change. Right now when a contact is qualified, it's immediately marked as UNAVAILABLE. If a

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread George Joseph
On Sat, Mar 28, 2015 at 6:48 PM, Joshua Colp jc...@digium.com wrote: George Joseph wrote: I've been trying to figure out how to get more control of the pjsip_options qualify process. Specifically, how to get a timely positive indication of failure and how to generate events on a status

Re: [asterisk-dev] RFC: Refactor qualify and res_pjsip/endpt_send_request

2015-03-28 Thread George Joseph
On Sat, Mar 28, 2015 at 6:53 PM, Joshua Colp jc...@digium.com wrote: snip all the things G, it requires an rdata. I'll ponder further. Eagerly awaiting the results of the ponder while continuing the investigation myself. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan