[asterisk-app-dev] Send a SIP NOTIFY via a softphone, not via Asterisk

[Mark Michelson]

Hello,

Asterisk is not a SIP proxy, so it does not forward SIP traffic to 
destinations. In your case, you're likely seeing a 489 response because 
Asterisk only knows about specific events in NOTIFY requests ("refer" 
for transfers, "message-summary" for outbound MWI subscriptions, 
"keep-alive" for certain devices' NAT keepalives, and "call-completion" 
for call completion subscriptions. Anything else is not understood by 
Asterisk, so you get a 489 Bad Event response.

If you want to send NOTIFYs from Asterisk, you must use AMI or the CLI 
commands to do so.

On 04/28/2015 10:05 AM, Ludovic Gasc wrote:
> Hi,
>
> I've a SIP endpoint written in Python-AsyncIO that is registered on an 
> Asterisk 13 with chan_sip.
>
> When I try to send a SIP NOTIFY to another hardphone endpoint (it's to 
> send commands), Asterisk anwsers me with: "SIP/2.0 489 Bad event"
>
> In Asterisk, even with debug level on SIP and in console, I don't have 
> a very interesting message:
> [Apr 28 16:57:48] DEBUG[2932]: chan_sip.c:28297 handle_request_do: SIP 
> message could not be handled, bad request: 
> b5262f5c-9061-4cb3-86c6-df629fd95a82
>
> An idea to have more details about this error ? Or it's better to use 
> pjsip ?
>
> BTW, is it possible to send a SIP NOTIFY to another endpoint via 
> Asterisk, or it's forbidden ?
>
> PS: I already know it's possible to send SIP NOTIFY via AMI, I've 
> already used that.
> But the idea here it's a tool where we don't need an AMI access with 
> Asterisk to run.
>
> Regards.
> --
> Ludovic Gasc (GMLudo)
> http://www.gmludo.eu/
>
>
> _______________________________________________
> asterisk-app-dev mailing list
> asterisk-app-dev at lists.digium.com
> http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-app-dev/attachments/20150429/01801a92/attachment.html>