VIDEOCHAT  ::   FAQ  ::   Поиск  ::   Регистрация  ::   Вход

BLF на телефоне YEALINK T27P

Новичком считается только что прочитавший «Астериск - будущее телефонии»
http://asterisk.ru/knowledgebase/books
и пытающийся сделать большее

Модераторы: april22, Zavr2008

Ответить
pendolf1984
Сообщения: 4
Зарегистрирован: 27 янв 2017, 21:40

BLF на телефоне YEALINK T27P

Сообщение pendolf1984 »

Добрый день.
Имеется Asterisk 13.8 и телефон Yealink T27P с панелью расширения EXP20, одна кнопка настроена на мониторинг статуса абонента, но лампочка статуса не загорается. Статус при звонке и разговоре не меняется.

Код: Выделить всё

asterisk*CLI> core show hints

    -= Registered Asterisk Dial Plan Hints =-
6003@blf            : Dial                  State:Unavailable     Presence:not_set         Watchers  0
6002@blf            : Dial                  State:Unavailable     Presence:not_set         Watchers  0
6012@blf            : Dial                  State:Unavailable     Presence:not_set         Watchers  1
----------------
- 3 hints registered

Код: Выделить всё

asterisk*CLI> sip show subscriptions
Peer             User             Call ID          Extension        Last state     Type            Mailbox    Expiry
192.168.3.98     "Бурмист  0_4208256384@19  6012@blf         Unavailable    dialog-info+xml <none>     001800
1 active SIP subscription
Подскажите пожалуйста, в чем может быть проблема?
Вернуться к началу
virus_net
Сообщения: 2337
Зарегистрирован: 05 июн 2013, 08:12
Откуда: Москва

Re: BLF на телефоне YEALINK T27P

Сообщение virus_net »

А что показывает траблшут ?
мой SIP URI sip:virus_net@asterisk.ru
bitname.ru - Домены .bit (namecoin) .emc .coin .lib .bazar (emercoin)
ENUMER - звони бесплатно и напрямую.
Вернуться к началу
pendolf1984
Сообщения: 4
Зарегистрирован: 27 янв 2017, 21:40

Re: BLF на телефоне YEALINK T27P

Сообщение pendolf1984 »

PRIME_BBCODE_SPOILER_SHOW PRIME_BBCODE_SPOILER:
asterisk*CLI> sip set debug peer 6003
SIP Debugging Enabled for IP: 192.168.3.98

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6012@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK3198190529
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
To: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
Call-ID: 0_2649867703@192.168.3.98
CSeq: 81 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="550291b1", uri="sip:6012@192.168.0.15:5060", response="3fc5dd1b1c99cfb4cf32024e5cd9dc84", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 0
Event: dialog
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Found peer '6003' for '6003' from 192.168.3.98:5060
[Jan 28 12:28:48] NOTICE[1159]: chan_sip.c:17156 check_auth: Correct auth, but based on stale nonce received from '"T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575'

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK3198190529;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
To: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
Call-ID: 0_2649867703@192.168.3.98
CSeq: 81 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="47775647", stale=true
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_2649867703@192.168.3.98' in 6400 ms (Method: SUBSCRIBE)

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6012@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK730837871
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
To: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
Call-ID: 0_2649867703@192.168.3.98
CSeq: 82 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="47775647", uri="sip:6012@192.168.0.15:5060", response="cf833470edca576d5e169aa5c6f306e1", algorithm=MD5
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 0
Event: dialog
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Found peer '6003' for '6003' from 192.168.3.98:5060
Looking for 6012 in blf (domain 192.168.0.15)

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK730837871;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
To: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
Call-ID: 0_2649867703@192.168.3.98
CSeq: 82 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 0
Content-Length: 0


<------------>
set_destination: Parsing <sip:6003@192.168.3.98:5060> for address/port to send to
set_destination: set destination to 192.168.3.98:5060
Reliably Transmitting (no NAT) to 192.168.3.98:5060:
NOTIFY sip:6003@192.168.3.98:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK7e76ab21
Max-Forwards: 70
From: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
Contact: <sip:6012@192.168.0.15:5060>
Call-ID: 0_2649867703@192.168.3.98
CSeq: 142 NOTIFY
User-Agent: 1MF
Subscription-State: terminated;reason=timeout
Event: dialog
Content-Type: application/dialog-info+xml
Content-Length: 211

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="40" state="full" entity="sip:6012@192.168.0.15:5060">
<dialog id="6012">
<state>terminated</state>
</dialog>
</dialog-info>

---

<--- SIP read from UDP:192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK7e76ab21
From: <sip:6012@192.168.0.15:5060>;tag=as78ff64e9
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=1742314575
Call-ID: 0_2649867703@192.168.3.98
CSeq: 142 NOTIFY
Contact: <sip:6003@192.168.3.98:5060>
User-Agent: Yealink SIP-T27P 45.81.0.25
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Really destroying SIP dialog '0_2649867703@192.168.3.98' Method: SUBSCRIBE

<--- SIP read from UDP:192.168.3.98:5060 --->
REGISTER sip:192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK4175449406
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=3399004685
To: "T27P" <sip:6003@192.168.0.15:5060>
Call-ID: 0_4198889057@192.168.3.98
CSeq: 633 REGISTER
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="77427fd2", uri="sip:192.168.0.15:5060", response="a5d4dd821bb4cdec4a7168729b456acd", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 0
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
Sending to 192.168.3.98:5060 (no NAT)

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK4175449406;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=3399004685
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=as4734d4a7
Call-ID: 0_4198889057@192.168.3.98
CSeq: 633 REGISTER
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="4cd7011b"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_4198889057@192.168.3.98' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.3.98:5060 --->
REGISTER sip:192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK31895279
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=3399004685
To: "T27P" <sip:6003@192.168.0.15:5060>
Call-ID: 0_4198889057@192.168.3.98
CSeq: 634 REGISTER
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="4cd7011b", uri="sip:192.168.0.15:5060", response="978120e0589cd174ab4b552bdc9cde19", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 0
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
-- Unregistered SIP '6003'

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK31895279;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=3399004685
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=as4734d4a7
Call-ID: 0_4198889057@192.168.3.98
CSeq: 634 REGISTER
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 0
Date: Sat, 28 Jan 2017 09:28:49 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_4198889057@192.168.3.98' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.3.98:5060 --->
REGISTER sip:192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1010099943
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=287323887
To: "T27P" <sip:6003@192.168.0.15:5060>
Call-ID: 0_800558100@192.168.3.98
CSeq: 1 REGISTER
Contact: <sip:6003@192.168.3.98:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 300
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (13 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
Sending to 192.168.3.98:5060 (no NAT)

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1010099943;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=287323887
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=as06d88109
Call-ID: 0_800558100@192.168.3.98
CSeq: 1 REGISTER
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="74cbea67"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_800558100@192.168.3.98' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.3.98:5060 --->
REGISTER sip:192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1825190708
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=287323887
To: "T27P" <sip:6003@192.168.0.15:5060>
Call-ID: 0_800558100@192.168.3.98
CSeq: 2 REGISTER
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="74cbea67", uri="sip:192.168.0.15:5060", response="3684139d6b88430d1b29ed608edab78d", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 300
Allow-Events: talk,hold,conference,refer,check-sync
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
-- Registered SIP '6003' at 192.168.3.98:5060
Reliably Transmitting (no NAT) to 192.168.3.98:5060:
OPTIONS sip:6003@192.168.3.98:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK428394ec
Max-Forwards: 70
From: "asterisk" <sip:asterisk@192.168.0.15>;tag=as079c9bd6
To: <sip:6003@192.168.3.98:5060>
Contact: <sip:asterisk@192.168.0.15:5060>
Call-ID: 5b147b1659b195ea735acdff79befe25@192.168.0.15:5060
CSeq: 102 OPTIONS
User-Agent: 1MF
Date: Sat, 28 Jan 2017 09:28:53 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


---

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1825190708;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=287323887
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=as06d88109
Call-ID: 0_800558100@192.168.3.98
CSeq: 2 REGISTER
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 300
Contact: <sip:6003@192.168.3.98:5060>;expires=300
Date: Sat, 28 Jan 2017 09:28:53 GMT
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_800558100@192.168.3.98' in 32000 ms (Method: REGISTER)

<--- SIP read from UDP:192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK428394ec
From: "asterisk" <sip:asterisk@192.168.0.15>;tag=as079c9bd6
To: <sip:6003@192.168.3.98:5060>;tag=2158808661
Call-ID: 5b147b1659b195ea735acdff79befe25@192.168.0.15:5060
CSeq: 102 OPTIONS
User-Agent: Yealink SIP-T27P 45.81.0.25
Content-Length: 0

<------------->
--- (8 headers 0 lines) ---
Really destroying SIP dialog '5b147b1659b195ea735acdff79befe25@192.168.0.15:5060' Method: OPTIONS

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6003@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK3143317363
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1423388950
To: <sip:6003@192.168.0.15:5060>
Call-ID: 0_2209175949@192.168.3.98
CSeq: 1 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Accept: application/reginfo+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 330
Event: reg
Content-Length: 0

<------------->
--- (13 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
Creating new subscription
Sending to 192.168.3.98:5060 (no NAT)
sip_route_dump: route/path hop: <sip:6003@192.168.3.98:5060>
Found peer '6003' for '6003' from 192.168.3.98:5060

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK3143317363;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1423388950
To: <sip:6003@192.168.0.15:5060>;tag=as7ddaa260
Call-ID: 0_2209175949@192.168.3.98
CSeq: 1 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="738d427f"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_2209175949@192.168.3.98' in 9344 ms (Method: SUBSCRIBE)

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6012@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1798572864
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
To: <sip:6012@192.168.0.15:5060>
Call-ID: 0_3752924677@192.168.3.98
CSeq: 1 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 1800
Event: dialog
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Sending to 192.168.3.98:5060 (no NAT)
Creating new subscription
Sending to 192.168.3.98:5060 (no NAT)
sip_route_dump: route/path hop: <sip:6003@192.168.3.98:5060>
Found peer '6003' for '6003' from 192.168.3.98:5060

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1798572864;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
To: <sip:6012@192.168.0.15:5060>;tag=as07bbe4ef
Call-ID: 0_3752924677@192.168.3.98
CSeq: 1 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="11e557e6"
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog '0_3752924677@192.168.3.98' in 9344 ms (Method: SUBSCRIBE)

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6012@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1484704602
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
To: <sip:6012@192.168.0.15:5060>
Call-ID: 0_3752924677@192.168.3.98
CSeq: 2 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="11e557e6", uri="sip:6012@192.168.0.15:5060", response="379201424c82de440effa4c79c33cbf9", algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 1800
Event: dialog
Content-Length: 0

<------------->
--- (15 headers 0 lines) ---
Creating new subscription
Sending to 192.168.3.98:5060 (no NAT)
Found peer '6003' for '6003' from 192.168.3.98:5060
Looking for 6012 in blf (domain 192.168.0.15)
Scheduling destruction of SIP dialog '0_3752924677@192.168.3.98' in 1810000 ms (Method: SUBSCRIBE)

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK1484704602;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
To: <sip:6012@192.168.0.15:5060>;tag=as07bbe4ef
Call-ID: 0_3752924677@192.168.3.98
CSeq: 2 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 1800
Contact: <sip:6012@192.168.0.15:5060>;expires=1800
Content-Length: 0


<------------>
set_destination: Parsing <sip:6003@192.168.3.98:5060> for address/port to send to
set_destination: set destination to 192.168.3.98:5060
Reliably Transmitting (no NAT) to 192.168.3.98:5060:
NOTIFY sip:6003@192.168.3.98:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK41ad59cd
Max-Forwards: 70
From: <sip:6012@192.168.0.15:5060>;tag=as07bbe4ef
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
Contact: <sip:6012@192.168.0.15:5060>
Call-ID: 0_3752924677@192.168.3.98
CSeq: 102 NOTIFY
User-Agent: 1MF
Subscription-State: active
Event: dialog
Content-Type: application/dialog-info+xml
Content-Length: 210

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:6012@192.168.0.15:5060">
<dialog id="6012">
<state>terminated</state>
</dialog>
</dialog-info>

---

<--- SIP read from UDP:192.168.3.98:5060 --->
SUBSCRIBE sip:6003@192.168.0.15:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK319076200
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1423388950
To: <sip:6003@192.168.0.15:5060>
Call-ID: 0_2209175949@192.168.3.98
CSeq: 2 SUBSCRIBE
Contact: <sip:6003@192.168.3.98:5060>
Authorization: Digest username="6003", realm="asterisk", nonce="738d427f", uri="sip:6003@192.168.0.15:5060", response="d0d5d1ec8ed14def0a09026e27122ebc", algorithm=MD5
Accept: application/reginfo+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T27P 45.81.0.25
Expires: 330
Event: reg
Content-Length: 0

<------------->
--- (14 headers 0 lines) ---
Creating new subscription
Sending to 192.168.3.98:5060 (no NAT)
Found peer '6003' for '6003' from 192.168.3.98:5060

<--- Transmitting (no NAT) to 192.168.3.98:5060 --->
SIP/2.0 489 Bad Event
Via: SIP/2.0/UDP 192.168.3.98:5060;branch=z9hG4bK319076200;received=192.168.3.98
From: "T27P" <sip:6003@192.168.0.15:5060>;tag=1423388950
To: <sip:6003@192.168.0.15:5060>;tag=as7ddaa260
Call-ID: 0_2209175949@192.168.3.98
CSeq: 2 SUBSCRIBE
Server: 1MF
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


<------------>
Really destroying SIP dialog '0_2209175949@192.168.3.98' Method: SUBSCRIBE

<--- SIP read from UDP:192.168.3.98:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.15:5060;branch=z9hG4bK41ad59cd
From: <sip:6012@192.168.0.15:5060>;tag=as07bbe4ef
To: "T27P" <sip:6003@192.168.0.15:5060>;tag=1466230643
Call-ID: 0_3752924677@192.168.3.98
CSeq: 102 NOTIFY
Contact: <sip:6003@192.168.3.98:5060>
User-Agent: Yealink SIP-T27P 45.81.0.25
Content-Length: 0

<------------->
--- (9 headers 0 lines) ---
Really destroying SIP dialog '0_4198889057@192.168.3.98' Method: REGISTER
Вернуться к началу
ded
Сообщения: 15629
Зарегистрирован: 26 авг 2010, 19:00

Re: BLF на телефоне YEALINK T27P

Сообщение ded »

ТС, если State:Unavailable, то уже писать о том, что лампочка статуса не загорается и статус при звонке и разговоре не меняется не имеет смысла.
Ваша кнопка НЕ настроена на мониторинг статуса абонента,
Должны быть видны статусы
State:Busy
State:Idle
State:InUse
Вернуться к началу
pendolf1984
Сообщения: 4
Зарегистрирован: 27 янв 2017, 21:40

Re: BLF на телефоне YEALINK T27P

Сообщение pendolf1984 »

Кнопка настроена.
Изображение
Вернуться к началу
virus_net
Сообщения: 2337
Зарегистрирован: 05 июн 2013, 08:12
Откуда: Москва

Re: BLF на телефоне YEALINK T27P

Сообщение virus_net »

pendolf1984, как бы весь процесс состоит из более чем одного действия. как минимум:
  • - подписка
    - изменение состояния номера, который мониторится
    - отправка уведомления подписчику
Под:
virus_net писал(а):А что показывает траблшут ?
Все же подразумевалось траблшут всего процесса и всех его составляющих, а не только первого пункта.
Так же в вашем дебаге отсутствуют временные метки. Вот именно поэтому я предпочитаю tcpdump, а не sip debug в CLI.
Так же в дебаге смущает, что последняя попытка SUBSCRIBE завершилась 489 Bad Event, хотя до этого было 200 OK, но далее, после этого 200 ОК (правда не понятно через какое время) с сервера ушел NOTIFY с Subscription-State: terminated;reason=timeout

https://www.ietf.org/rfc/rfc3265.txt
If no refresh for a notification address is received before its expiration time, the subscription is removed. When removing a subscription, the notifier SHOULD send a NOTIFY message with a "Subscription-State" value of "terminated" to inform it that the subscription is being removed. If such a message is sent, the "Subscription-State" header SHOULD contain a "reason=timeout" parameter.
мой SIP URI sip:virus_net@asterisk.ru
bitname.ru - Домены .bit (namecoin) .emc .coin .lib .bazar (emercoin)
ENUMER - звони бесплатно и напрямую.
Вернуться к началу
pendolf1984
Сообщения: 4
Зарегистрирован: 27 янв 2017, 21:40

Re: BLF на телефоне YEALINK T27P

Сообщение pendolf1984 »

Тему можно закрывать. Я, что называется "сам дурак", неправильно hints прописал.
Вернуться к началу
Ответить

Вернуться в «Вопросы новичков»

© 2008 — 2025 Asterisk.ru
Digium, Asterisk and AsteriskNOW are registered trademarks of Digium, Inc.
Design and development by PostMet-Netzwerk GmbH