[asterisk-dev] BLF and unreachable phones

Dario Busso dario.busso at gmail.com
Fri Nov 27 03:22:56 CST 2009


The system is running Asterisk 1.4.26.2.
We are experiencing a misbehavior on the BLF on Linksys (SPA-942 and
SPA962) used as subscriptions in order to monitoring the phone state.
All work fine for the ringing, in-use and idle state instead it doesn't
work for unreachable state. We have test also Polycom and the issue
doesn't apply.
Does someone has find a solution for this?

Here the notification sip message sent to the Linksys device:

<--- SIP read from 192.168.16.118:5060 --->

SIP/2.0 200 OK

To: <sip:514 at 192.168.16.118:5060>;tag=c546d8c8453af440i0

From: "CLIP5500" <sip:CLIP5500 at 192.168.16.40>;tag=as41e6b4ac

Call-ID: 035f33a35687f1dd052ecd344b8b1ffd at 192.168.16.40

CSeq: 102 OPTIONS

Via: SIP/2.0/UDP 192.168.16.40:5060;branch=z9hG4bK7e0a0cd0

Server: Linksys/SPA962-6.1.5(a)

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: replaces

<------------->

--- (10 headers 0 lines) ---

Really destroying SIP dialog
'035f33a35687f1dd052ecd344b8b1ffd at 192.168.16.40' Meth

od: OPTIONS

set_destination: Parsing <sip:514 at 192.168.16.118:5060> for address/port
to send to

set_destination: set destination to 192.168.16.118, port 5060

Reliably Transmitting (NAT) to 192.168.16.118:5060:

NOTIFY sip:514 at 192.168.16.118:5060 SIP/2.0

Via: SIP/2.0/UDP 192.168.16.40:5060;branch=z9hG4bK23aaa13e;rport

From: <sip:516 at 192.168.16.40>;tag=as73ee4dd0

To: "514" <sip:514 at 192.168.16.40>;tag=a7ca5de211f2a1ff

Contact: <sip:516 at 192.168.16.40>

Call-ID: 34f739de-6e9d1633 at 192.168.16.118

CSeq: 121 NOTIFY

User-Agent: CLIP5500-3.0

Max-Forwards: 70

Event: dialog

Content-Type: application/dialog-info+xml

Subscription-State: active

Content-Length: 205

<?xml version="1.0"?>

<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="19"
state="full"

entity="sip:516 at 192.168.16.40">

<dialog id="516">

<state>terminated</state>

</dialog>

</dialog-info>


Dario Busso



More information about the asterisk-dev mailing list