|
Откуда: Мск
Сообщений: 129
|
Fanvil210+hold+mwi
Добрый день! Подскажите возможную проблему ...
Имеется аппарат с прошивкой от Fanvil210 v.1.7.130.93
Asterisk 1.6.0.26-FONCORE-r78 on trixbox
1. Проблема с hold:
- при нажатии hold
-- Called 106
-- SIP/106-00000096 is ringing
-- SIP/106-00000096 answered DAHDI/18-1
-- Started music on hold, class 'default', on DAHDI/18-1
повторное нажатие ни к чему не приводит, музыка продолжает играть ...
если звонить внутри офиса, hold отрабатывает нормально.
2. На телефоне есть индикатор сообщений голосовой почты. При том, что сообщение есть - индикатор не горит.
RTP Debugging Enabled for IP: 10.0.0.54 на телефоне:
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030358, ts 248906352, len 000160)
Sent RTP packet to 10.0.0.54:10014 (type 00, seq 035144, ts 134400, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030359, ts 248906512, len 000160)
Sent RTP packet to 10.0.0.54:10014 (type 00, seq 035145, ts 134560, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030360, ts 248906672, len 000160)
Sent RTP packet to 10.0.0.54:10014 (type 00, seq 035146, ts 134720, len 000160)
Sent RTP packet to 10.0.0.54:10014 (type 00, seq 035147, ts 134880, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030361, ts 248906832, len 000160)
-- Started music on hold, class 'default', on DAHDI/18-1
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030362, ts 248906992, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 030363, ts 248907152, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 017715, ts 1005354331, len 000160)
Got RTP packet from 10.0.0.54:10014 (type 00, seq 017716, ts 1005354491, len 000160)
sip set debug IP: 10.0.0.54 на телефоне:
<--- SIP read from UDP://10.0.0.54:5060 --->
REGISTER sip:asterisk SIP/2.0
Via: SIP/2.0/UDP 10.0.0.54:5060;branch=z9hG4bK197876713543116422;rport
From: 106 <sip:106@asterisk>;tag=243602069
To: 106 <sip:106@asterisk>
Call-ID: 168341014030206-190731022618561@10.0.0.54
CSeq: 80 REGISTER
Contact: <sip:106@10.0.0.54:5060>
Authorization: Digest username="106", realm="asterisk", nonce="48408640", uri="sip:asterisk", response="cba4c0d17a0c3f28cbec0e0e3c5e1333", algorithm=MD5
Max-Forwards: 70
Expires: 60
Supported: path
User-Agent: Voip Phone 1.0
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog '4691711421806-209154909923@10.0.0.54' in 32000 ms (Method: REGISTER)
trixbox*CLI>
<--- SIP read from UDP://10.0.0.54:5060 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.0.251:5060;branch=z9hG4bK37131be9;rport
From: "Unknown" <sip:Unknown@10.0.0.251>;tag=as1b1b097a
To: <sip:106@10.0.0.54:5060>
Call-ID: 0a6789672c3e93550690353155d6a4d8@10.0.0.251
CSeq: 102 OPTIONS
Contact: <sip:106@10.0.0.54:5060>
Supported: 100rel, replaces, timer
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REFER, NOTIFY, INFO, PRACK, UPDATE, MESSAGE
Accept: application/sdp, message/sipfrag, application/dtmf-relay
ontent-Length: 0
--- (13 headers 0 lines) ---
Sending to 10.0.0.54 : 5060 (no NAT)
Reliably Transmitting (no NAT) to 10.0.0.54:5060:
OPTIONS sip:106@10.0.0.54:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.251:5060;branch=z9hG4bK6c948ac2;rport
Max-Forwards: 70
From: "Unknown" <sip:Unknown@10.0.0.251>;tag=as3274625b
To: <sip:106@10.0.0.54:5060>
Contact: <sip:Unknown@10.0.0.251>
Call-ID: 2ae8d3c44f295c877c7e103c0bc17e9c@10.0.0.251
CSeq: 102 OPTIONS
User-Agent: Cisco-SIPGateway/IOS-12.x
Date: Thu, 02 Dec 2010 09:47:16 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0
|
