<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Steve Totaro wrote:
<blockquote
id="mid_ea18e54a0806111055v3b80e808o5194f402cba169d3_mail_gmail_com"
cite="mid:ea18e54a0806111055v3b80e808o5194f402cba169d3@mail.gmail.com"
type="cite">
<pre wrap="">On Wed, Jun 11, 2008 at 1:47 PM, Steve Totaro
<a class="moz-txt-link-rfc2396E" href="mailto:stotaro@totarotechnologies.com"><stotaro@totarotechnologies.com></a> wrote:
</pre>
<blockquote id="StationeryCiteGenerated_1" type="cite">
<pre wrap="">On Wed, Jun 11, 2008 at 11:53 AM, Raj Jain <a class="moz-txt-link-rfc2396E" href="mailto:rj2807@gmail.com"><rj2807@gmail.com></a> wrote:
</pre>
<blockquote id="StationeryCiteGenerated_2" type="cite">
<pre wrap="">On Wed, Jun 11, 2008 at 9:17 AM, Brian J. Murrell <a class="moz-txt-link-rfc2396E" href="mailto:brian@interlinx.bc.ca"><brian@interlinx.bc.ca></a> wrote:
</pre>
<blockquote id="StationeryCiteGenerated_3" type="cite">
<pre wrap="">I'm wondering if the SIP lines can start ringing as soon as the zap line
gets a call and when the zap line finally gets the CID, that is passed
down to the already ringing SIP phones.
</pre>
</blockquote>
<pre wrap="">This is actually an interesting problem. The SIP protocol didn't
originally support this notion, but a recent extension to SIP adds
this capability to the protocol. This concept is known as
Connected-Identity in SIP and is defined in RFC 4916. The idea is to
be able to update remote party's identity in either direction after
the call has been answered or while it is ringing. I don't think
people were really aware of the scenario that you've described, but it
is an interesting one and I think RFC 4916 covers it.
The thing though is that even if somebody added this capability to
Asterisk, you'll need SIP phones that support this capability as well.
Right now, I don't think there is any SIP phone out there that
supports this.
--
Raj Jain
</pre>
</blockquote>
<pre wrap="">If you search the archives, you will see this topic come up again and
again, and in reality it is an issue. If nobody answers a phone in
say five to ten seconds (including voicemail), I hangup.
Ok, then build it in now. Make it work for DAHDI and when the phones
start implementing the capability, Asterisk will be ready. People
with channel banks or similar can benefit immediately.
Thanks,
Steve Totaro
</pre>
</blockquote>
<pre wrap=""><!---->
Correction, seconds should read rings.</pre>
</blockquote>
On the subject of CallerID and ringing, I'm not sure if it's like this
everywhere in the US, but where I live in Texas, our caller ID signal
is sent between the first and second rings. If the phone is answered
in the middle of the first ring then CID signal is never received.
This might not be an issue in the scenario being discussed, because it
sounds more like you're asking for Asterisk to connect the ringing Zap
channel to a sip line before issuing an "answer" in the dialplan.
Correct me if I'm wrong. I'm more used to using Asterisk in a PBX
context with an automated attendant that answers every call before
ringing any of the extensions. The direct Zap to Sip without without a
menu is more of a switch context correct?<br>
<br>
-Brent<br>
</body>
</html>