DVG-2004s
Откуда: Уфа
Сообщений: 5856
|
Re: DVG-2004s
если и дальше будешь отвечать в таком духе, тебе придется ждать штатных форумных телепатов. но они заходят сюда редко.
объясняй подробно что и как делаешь. по какому протоколу подключился к шлюзу slmonом? нужно по udp. и правильно вводить пароль/логин если есть
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
DVG-2004s
Default Codec G.711 uLaw
DTMF Method SIP Info
Register By
SIP Setting
Register By Port
Request-URI 701
Login Name 701
Password *****
Port No. 5060
Register Server IP Address 192.168.0.X
Register Server Port No. 0
Outbound Proxy 192.168.0.X
Outbound Proxy Port No. 5060
Register Expires 6 sec (default: 3600sec)
Start Media Port start:41000
Session timer 180sec
SessionType Reinvite
Session Refresher None
Pre-Ack Enable
UPnP Disable
STUN Server IP Address Dsiable
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
шлюз веб интерфейсе стоит на адрессе 192.168.0.6:9999
подключаюсь, через UDP local port 9999, port 5061 , ок и он выводит только одну строчку которую я ранее написал..
|
Откуда: Уфа
Сообщений: 5856
|
Re: DVG-2004s
"шлюз веб интерфейсе стоит на адрессе 192.168.0.6:9999 "
это что значит? просто запускайте slmon и введите ip адрес шлюза
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
что бы зайти на шлюз через веб интерфейс я в вожжу адрес х.х.х.х:9999,
в slmon ввожу IP порт 5061 local poort 9999 login, password enter
дальше он выводит строчку
14:30:40 to connect Server IP=<192.168.0.6>, port=5061, local port:9999
и всё..
может сделать чего надо еще, чтоб лог показал?
P.S.:порты менял, не помогает..
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
а по настройкам которые есть ни чего сказать нельзя?
почему не выходит на*?
|
Откуда: Уфа
Сообщений: 5856
|
Re: DVG-2004s
зайди на астериск сделай set verbose 5
sip set debug ip 192.168.0.6
сделай звонок и пришли результат сюда
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
при звонке с телефона на порту DVG
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
Retransmitting #4 (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK21781f13;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as56b319ca
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 147bf9980ad379506d0255cd5132a3b2@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:10:01 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
Really destroying SIP dialog '147bf9980ad379506d0255cd5132a3b2@192.168.0.1' Method: OPTIONS
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK21781f13;rport
4U└*From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as56b319ca
To: <sip:192.168.0.6>
Call-ID: 147bf9980ad379506d0255cd5132a3b2@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
при звонке на телефон
<------------->
--- (7 headers 0 lines) ---
Retransmitting #4 (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK7a9e56ac;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as701f61ea
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 3790b56267d1a4e751ef34db5aed9fa5@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:11:25 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
Really destroying SIP dialog '3790b56267d1a4e751ef34db5aed9fa5@192.168.0.1' Method: OPTIONS
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK7a9e56ac;rport
LB х7.╟z From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as701f61ea
To: <sip:192.168.0.6>
Call-ID: 3790b56267d1a4e751ef34db5aed9fa5@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
Retransmitting #4 (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK0ae68920;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as0c90256f
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 3c45c75032a1c3b13c5558316dcee27d@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:11:25 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
Really destroying SIP dialog '3c45c75032a1c3b13c5558316dcee27d@192.168.0.1' Method: OPTIONS
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK0ae68920;rport
LB х7.╟z From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as0c90256f
To: <sip:192.168.0.6>
Call-ID: 3c45c75032a1c3b13c5558316dcee27d@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
|
Откуда: гюХабаровск
Сообщений: 97
|
Re: DVG-2004s
при разговоре
Scheduling destruction of SIP dialog 'REGISTER_001346E0DEF0_T590397@192.168.0.6' in 32000 ms (Method: REGISTER)
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK_001346E0DEF0_T0009024A
Max-Forwards: 70
From: <sip:704@192.168.0.1>;tag=001346E0DEF0_T590410
To: <sip:704@192.168.0.1>
Call-ID: REGISTER_001346E0DEF0_T590410@192.168.0.6
CSeq: 1288494932 REGISTER
Contact: <sip:704@192.168.0.6:5060>
Expires: 6
User-Agent: ACT G1104S 01.02
Content-Length: 0
<------------->
--- (11 headers 0 lines) ---
Using latest REGISTER request as basis request
Sending to 192.168.0.6 : 5060 (no NAT)
<--- Transmitting (no NAT) to 192.168.0.6:5060 --->
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.0.6:5060;branch=z9hG4bK_001346E0DEF0_T0009024A;received=192.168.0.6
From: <sip:704@192.168.0.1>;tag=001346E0DEF0_T590410
To: <sip:704@192.168.0.1>;tag=as27435c6c
Call-ID: REGISTER_001346E0DEF0_T590410@192.168.0.6
CSeq: 1288494932 REGISTER
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
<------------>
Scheduling destruction of SIP dialog 'REGISTER_001346E0DEF0_T590410@192.168.0.6' in 32000 ms (Method: REGISTER)
Reliably Transmitting (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK7bba1eb6;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as3217f928
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 34ee99b279c3e7815ba8d8003a8138e7@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:12:21 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK7bba1eb6;rport
╛From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as3217f928
To: <sip:192.168.0.6>
Call-ID: 34ee99b279c3e7815ba8d8003a8138e7@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
Reliably Transmitting (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3dd9af95;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as680d86f7
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 2bca8de91c4e7944584d3f5408b5cc8b@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:12:21 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK3dd9af95;rport
╛From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as680d86f7
To: <sip:192.168.0.6>
Call-ID: 2bca8de91c4e7944584d3f5408b5cc8b@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
Reliably Transmitting (NAT) to 192.168.0.6:5060:
OPTIONS sip:192.168.0.6 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK67ae7c7a;rport
From: "Unknown" <sip:Unknown@192.168.0.1>;tag=as50eedabb
To: <sip:192.168.0.6>
Contact: <sip:Unknown@192.168.0.1>
Call-ID: 55e406fb2822e27c332dad3026598bdb@192.168.0.1
CSeq: 102 OPTIONS
User-Agent: Asterisk PBX
Max-Forwards: 70
Date: Wed, 29 Apr 2009 04:12:21 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0
---
trixbox1*CLI>
<--- SIP read from 192.168.0.6:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 192.168.0.1:5060;branch=z9hG4bK67ae7c7a;rport
╛From: "Unknown"<sip:Unknown@192.168.0.1>;tag=as50eedabb
To: <sip:192.168.0.6>
Call-ID: 55e406fb2822e27c332dad3026598bdb@192.168.0.1
CSeq: 102 OPTIONS
Content-Length: 0
<------------->
--- (7 headers 0 lines) ---
|
|