code for "call declined"
cmw
In my account with my SIP provider, flowroute.com, my incoming number
from the PSTN is configured to first try SIP registration, then if
that fails, to "failover" to my google voice number, where my
voicemail can pick up the call.
If Telephone is not running, that works OK. However, if Telephone is
running and I click "Decline" thinking to send the call to voicemail,
the call does not go to voicemail. Instead, the caller gets a busy
signal or some weird recorded message from PSTN about privacy
settings.
The provider says they are doing this correctly, following the RFC,
because Telephone sends a 603 message which they say:
> a 603 response is a global busy signal which means that the request should not be attempted to
> any other endpoint. This is the exact language from the SIP RFC defining the meaning of the 603 > response:
> 21.6.2 603 Decline
> The callee's machine was successfully contacted
> but the user explicitly does not wish to or cannot participate.
> The response MAYindicate a better time to call in the Retry-After header field.
> This status response is returned only if the client knows that no other
> end point will answer the request.
> The important clause here is that "status response
> is returned only if the client knows that no other end point will answer the request."
I wonder if Telephone, since it does not implement an answering
machine on its own, should be sending a different code to reject the
call?
Thank you.
Alexei Kuznetsov
Good point! I guess, we could do something like this: when you hit Decline, it will still send 603 Decline, but if you hold Option key when clicking Decline button, it will send 486 Busy Here reply. Will sending 486 code work for you?
Alexei
Ken Gillett
> --
> You received this message because you are subscribed to the Google Groups "Telephone Discussions" group.
> To post to this group, send email to teleph...@googlegroups.com.
> To unsubscribe from this group, send email to telephone-ap...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/telephone-app?hl=en.
>
Ken G i l l e t t
_/_/_/_/_/_/_/_/
Alexei Kuznetsov
Alexei
Alexei Kuznetsov
Alejandro Orellana
Other softphones send 603 in this scenario. 486 to me is not valid in this scenario.
In your case seems like your ITSP behaves this way.
My two cents.
Sent from my iPad
Alexei Kuznetsov
Alejandro, why ‘Busy Here’ is not valid in your case?
Alexei
cmw
Acrobits Softphone, the most popular softphone for the iPhone/iPod
touch, works the way I expect it to. Don't know what code it sends,
but when I reject the call it does go to voicemail.
Thank you.
On Apr 4, 6:32 am, Alejandro Orellana <chilote.orell...@gmail.com>
wrote:
> Another data point here
> Other softphones send 603 in this scenario. 486 to me is not valid in this scenario.
> In your case seems like your ITSP behaves this way.
>
> My two cents.
>
> Sent from my iPad
>
> On Apr 4, 2010, at 6:05 AM, Alexei Kuznetsov <eofs...@gmail.com> wrote:> Yes, maybe. It looks like section “13.3.1.3 The INVITE is Rejected” of RFC 3261 states that we should send 486 (or 600 otherwise).
Alejandro Orellana
Alejandro Orellana
13.3.1.3 The INVITE is Rejected A common scenario occurs when the callee is currently not willing or able to take additional calls at this end system. A 486 (Busy Here) SHOULD be returned in such a scenario. If the UAS knows that no other end system will be able to accept this call, a 600 (Busy Everywhere) response SHOULD be sent instead. However, it is unlikely that a UAS will be able to know this in general, and thus this response will not usually be used. The response is passed to the INVITE server transaction, which will deal with its retransmissions. A UAS rejecting an offer contained in an INVITE SHOULD return a 488 (Not Acceptable Here) response. Such a response SHOULD include a Warning header field value explaining why the offer was rejected.
21.4.24 486 Busy Here The callee's end system was contacted successfully, but the callee is currently not willing or able to take additional calls at this end system. The response MAY indicate a better time to call in the Retry-After header field. The user could also be available elsewhere, such as through a voice mail service. Status 600 (Busy Everywhere) SHOULD be used if the client knows that no other end system will be able to accept this call.
21.6.1 600 Busy Everywhere The callee's end system was contacted successfully but the callee is busy and does not wish to take the call at this time. The response MAY indicate a better time to call in the Retry-After header field. If the callee does not wish to reveal the reason for declining the call, the callee uses status code 603 (Decline) instead. This status response is returned only if the client knows that no other end point (such as a voice mail system) will answer the request. Otherwise, 486 (Busy Here) should be returned. 21.6.2 603 Decline The callee's machine was successfully contacted but the user explicitly does not wish to or cannot participate. The response MAY indicate a better time to call in the Retry-After header field. This status response is returned only if the client knows that no other end point will answer the request.