GXP2020 und Telekom Entertain IP

Sidebar Sidebar
Upgrade 3CX to v18 and get it hosted free!
M

M112

Neuer User
Mitglied seit
11 Jun 2010
Beiträge
1
Punkte für Reaktionen
0
Punkte
1
Hallo VoIP'ler,

bin jetzt auch einer von Euch. Aber meine aktuelle Konfiguration bringt mich langsam aber sicher zum Verzweifeln. Prinzipiell funktioniert alles, aber:

- Line 1 ist manchmal not registerd, oft direkt nach den Boot des Telefons, manchmal aber auch mal so zwischendurch
- Telefon klingelt nicht (sporadisch), am Speedport schon

Ich hab keine Idee woran es liegen könnte, mal geht's - mal nicht.

Noch ein paar Details:
Firmware: 1.2.4.3
Router: Speedport W920V, FW: 65.04.78
3 SIP Accounts von der Telekom, konfiguriert in Speedport und GS

Anbei noch ein Log, was mir aufgefallen ist, ist das Line 1 für eine Kürzere Zeit registriert wird, und nach der hälfte der Zeit wieder re-registriert. Die Abstände halbieren sich nach jedem Versuch.

Hat jemand deine Idee?

thx
M112 - der Neuling

Code: 
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] HW_status[0]=0 HW_status[1]=0	192.168.2.112	05/11 17:59:40.412	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] New DHCP IP address: 192.168.2.112	192.168.2.112	05/11 18:00:17.830	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Starting driver syslog...	192.168.2.112	05/11 18:00:17.861	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Grandstream GXP2020 gxp2020e.bin:1.2.4.3 boot55e.bin:1.1.6.9	192.168.2.112	05/11 18:00:18.251	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] DNS response received.	192.168.2.112	05/11 18:00:19.296	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Record found and about to process.	192.168.2.112	05/11 18:00:19.296	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Start processing DNS response message.	192.168.2.112	05/11 18:00:19.312	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SUCCESSFUL. result_ip is not 0; call callback function.	192.168.2.112	05/11 18:00:19.312	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Local time updated via NTP, next NTP sync in 3600 seconds	192.168.2.112	05/11 18:00:19.358	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Provision attempt 1	192.168.2.112	05/11 18:00:20.263	
<12>GS_LOG: [00:0B:82:24:AB:2C][708][9620000804A][01020403] File Not Found: cfg000b8224ab2c	192.168.2.112	05/11 18:00:20.419	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] DNS response received.	192.168.2.112	05/11 18:00:34.537	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Record found and about to process.	192.168.2.112	05/11 18:00:34.537	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Start processing DNS response message.	192.168.2.112	05/11 18:00:34.537	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SUCCESSFUL. result_ptr and callback are not NULL; call callback function.	192.168.2.112	05/11 18:00:34.537	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP_REGISTER: DNS A resolved to 1 records.  Record_1=217.0.16.90;	192.168.2.112	05/11 18:00:34.553	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 10001 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:00:34.553	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 559, sip_handle: 0x0051F8AA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5060;branch=z9hG4bKfd0a46c795a02a7e  From: <sip:[email protected]>;tag=798ff8	192.168.2.112	05/11 18:00:34.568	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(543, Account1): SIP/2.0 401 Unauthorized  Via: SIP/2.0/UDP 192.168.2.112:5060;rport=62212;received=87.157.196.37;branch=z9hG4bKfd0a46c795a02a7e  To: <sip:[email protected]>;	192.168.2.112	05/11 18:00:34.646	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 401	192.168.2.112	05/11 18:00:34.646	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 13	192.168.2.112	05/11 18:00:34.662	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 10002 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:00:34.662	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 876, sip_handle: 0x0051F8AA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5060;branch=z9hG4bKe570e14c16345f01  From: <sip:[email protected]>;tag=798ff8	192.168.2.112	05/11 18:00:34.662	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(628, Account1): SIP/2.0 200 OK  Via: SIP/2.0/UDP 192.168.2.112:5060;rport=62212;received=87.157.196.37;branch=z9hG4bKe570e14c16345f01  To: <sip:[email protected]>;tag=0e9261	192.168.2.112	05/11 18:00:34.693	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 200	192.168.2.112	05/11 18:00:34.693	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 13	192.168.2.112	05/11 18:00:34.693	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Line 1:REGISTERED for 648 seconds;re-REGISTER in 324 seconds	192.168.2.112	05/11 18:00:34.709	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] DNS response received.	192.168.2.112	05/11 18:00:36.503	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Record found and about to process.	192.168.2.112	05/11 18:00:36.518	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Start processing DNS response message.	192.168.2.112	05/11 18:00:36.518	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SUCCESSFUL. result_ptr and callback are not NULL; call callback function.	192.168.2.112	05/11 18:00:36.518	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP_REGISTER: DNS A resolved to 1 records.  Record_1=217.0.16.90;	192.168.2.112	05/11 18:00:36.518	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 20001 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8CA	192.168.2.112	05/11 18:00:36.534	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 558, sip_handle: 0x0051F8CA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5062;branch=z9hG4bKf1da54dcc76817cf  From: <sip:[email protected]>;tag=dc0065	192.168.2.112	05/11 18:00:36.550	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(542, Account2): SIP/2.0 401 Unauthorized  Via: SIP/2.0/UDP 192.168.2.112:5062;rport=5062;received=87.157.196.37;branch=z9hG4bKf1da54dcc76817cf  To: <sip:[email protected]>;t	192.168.2.112	05/11 18:00:36.581	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 401	192.168.2.112	05/11 18:00:36.596	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 14	192.168.2.112	05/11 18:00:36.596	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 20002 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8CA	192.168.2.112	05/11 18:00:36.596	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 875, sip_handle: 0x0051F8CA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5062;branch=z9hG4bK1e215011d1058ae4  From: <sip:[email protected]>;tag=dc0065	192.168.2.112	05/11 18:00:36.612	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(553, Account2): SIP/2.0 200 OK  Via: SIP/2.0/UDP 192.168.2.112:5062;rport=5062;received=87.157.196.37;branch=z9hG4bK1e215011d1058ae4  To: <sip:[email protected]>;tag=1b2a5ae	192.168.2.112	05/11 18:00:36.659	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 200	192.168.2.112	05/11 18:00:36.674	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 14	192.168.2.112	05/11 18:00:36.674	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Line 2:REGISTERED for 3600 seconds;re-REGISTER in 3000 seconds	192.168.2.112	05/11 18:00:36.674	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] DNS response received.	192.168.2.112	05/11 18:00:38.500	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Record found and about to process.	192.168.2.112	05/11 18:00:38.515	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Start processing DNS response message.	192.168.2.112	05/11 18:00:38.515	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SUCCESSFUL. result_ptr and callback are not NULL; call callback function.	192.168.2.112	05/11 18:00:38.531	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP_REGISTER: DNS A resolved to 1 records.  Record_1=217.0.16.90;	192.168.2.112	05/11 18:00:38.531	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 30001 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:00:38.546	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 558, sip_handle: 0x0051F8EA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5064;branch=z9hG4bK3835dc3b68f8bfc0  From: <sip:[email protected]>;tag=fe2329	192.168.2.112	05/11 18:00:38.546	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(542, Account3): SIP/2.0 401 Unauthorized  Via: SIP/2.0/UDP 192.168.2.112:5064;rport=5064;received=87.157.196.37;branch=z9hG4bK3835dc3b68f8bfc0  To: <sip:[email protected]>;t	192.168.2.112	05/11 18:00:38.578	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 401	192.168.2.112	05/11 18:00:38.593	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 15	192.168.2.112	05/11 18:00:38.593	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 30002 REGISTER To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:00:38.593	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 875, sip_handle: 0x0051F8EA, REGISTER sip:tel.t-online.de SIP/2.0  Via: SIP/2.0/UDP 192.168.2.112:5064;branch=z9hG4bKcf0841b1838d3b75  From: <sip:[email protected]>;tag=fe2329	192.168.2.112	05/11 18:00:38.624	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(553, Account3): SIP/2.0 200 OK  Via: SIP/2.0/UDP 192.168.2.112:5064;rport=5064;received=87.157.196.37;branch=z9hG4bKcf0841b1838d3b75  To: <sip:[email protected]>;tag=02e03a1	192.168.2.112	05/11 18:00:38.640	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 200	192.168.2.112	05/11 18:00:38.656	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 15	192.168.2.112	05/11 18:00:38.656	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Line 3:REGISTERED for 3600 seconds;re-REGISTER in 3000 seconds	192.168.2.112	05/11 18:00:38.671	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(1559, Account1): INVITE sip:[email protected]:5060;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  Max-Forwar	192.168.2.112	05/11 18:01:53.676	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 2	192.168.2.112	05/11 18:01:53.707	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog not matched	192.168.2.112	05/11 18:01:53.707	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 100 To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:01:53.707	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 357, sip_handle: 0x0051F8AA, SIP/2.0 100 Trying  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  From: <sip:[email protected];user=	192.168.2.112	05/11 18:01:53.723	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] INVITE From=<sip:[email protected];user=phone>;tag=7c18484f To=<sip:[email protected]:5060;transport=udp>	192.168.2.112	05/11 18:01:53.723	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 180 To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:01:53.723	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 588, sip_handle: 0x0051F8AA, SIP/2.0 180 Ringing  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  From: <sip:[email protected];user	192.168.2.112	05/11 18:01:53.738	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:01:53 Tone start (0): 68	192.168.2.112	05/11 18:01:53.801	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:01:53 LCD Callmode: CALLMODE_SPEAKERRING	192.168.2.112	05/11 18:01:53.801	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:01:53 Voc mode (0): CALLMODE_SPEAKERRING	192.168.2.112	05/11 18:01:53.801	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:01:53 Aud path (0): AUD_PATH_SPEAKERRING	192.168.2.112	05/11 18:01:53.801	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sending notifies from incoming call	192.168.2.112	05/11 18:01:53.816	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(380, Account1): CANCEL sip:[email protected]:5060;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  Max-Forward	192.168.2.112	05/11 18:02:01.819	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 5	192.168.2.112	05/11 18:02:01.835	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 0	192.168.2.112	05/11 18:02:01.835	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 200 To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:02:01.835	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 402, sip_handle: 0x0051F8AA, SIP/2.0 200 OK  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  From: <sip:[email protected];user=phon	192.168.2.112	05/11 18:02:01.850	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:01 Tone stop (0)	192.168.2.112	05/11 18:02:01.850	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:01 LCD Callmode: CALLMODE_NULL	192.168.2.112	05/11 18:02:01.850	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:01 Voc mode (0): CALLMODE_NULL	192.168.2.112	05/11 18:02:01.850	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:01 Aud path (0): AUD_PATH_NULL	192.168.2.112	05/11 18:02:01.866	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 487 To 217.0.16.90:5060, sip_handle: 0x0051F8AA	192.168.2.112	05/11 18:02:01.866	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 389, sip_handle: 0x0051F8AA, SIP/2.0 487 Request Cancelled  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  From: <sip:[email protected]	192.168.2.112	05/11 18:02:01.866	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sending notifies from sig remote_cancel	192.168.2.112	05/11 18:02:01.866	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(395, Account1): ACK sip:[email protected]:5060;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK86f843cd50199ee2c1a97ccdf6140607.bb039491  Max-Forwards: 	192.168.2.112	05/11 18:02:01.913	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 3	192.168.2.112	05/11 18:02:01.913	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog not matched	192.168.2.112	05/11 18:02:01.913	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(1559, Account3): INVITE sip:[email protected]:5064;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  Max-Forwar	192.168.2.112	05/11 18:02:12.880	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 2	192.168.2.112	05/11 18:02:12.911	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog not matched	192.168.2.112	05/11 18:02:12.911	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 100 To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:02:12.911	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 357, sip_handle: 0x0051F8EA, SIP/2.0 100 Trying  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  From: <sip:[email protected];user=	192.168.2.112	05/11 18:02:12.926	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] INVITE From=<sip:[email protected];user=phone>;tag=f3641919 To=<sip:[email protected]:5064;transport=udp>	192.168.2.112	05/11 18:02:12.926	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 180 To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:02:12.926	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 588, sip_handle: 0x0051F8EA, SIP/2.0 180 Ringing  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  From: <sip:[email protected];user	192.168.2.112	05/11 18:02:12.942	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:12 Tone start (0): 68	192.168.2.112	05/11 18:02:12.989	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:12 LCD Callmode: CALLMODE_SPEAKERRING	192.168.2.112	05/11 18:02:13.004	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:12 Voc mode (0): CALLMODE_SPEAKERRING	192.168.2.112	05/11 18:02:13.004	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:12 Aud path (0): AUD_PATH_SPEAKERRING	192.168.2.112	05/11 18:02:13.004	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sending notifies from incoming call	192.168.2.112	05/11 18:02:13.020	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(380, Account3): CANCEL sip:[email protected]:5064;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  Max-Forward	192.168.2.112	05/11 18:02:15.844	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 5	192.168.2.112	05/11 18:02:15.859	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog matched to channel 0	192.168.2.112	05/11 18:02:15.859	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 200 To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:02:15.859	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 402, sip_handle: 0x0051F8EA, SIP/2.0 200 OK  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  From: <sip:[email protected];user=phon	192.168.2.112	05/11 18:02:15.875	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:15 Tone stop (0)	192.168.2.112	05/11 18:02:15.875	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:15 LCD Callmode: CALLMODE_NULL	192.168.2.112	05/11 18:02:15.875	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:15 Voc mode (0): CALLMODE_NULL	192.168.2.112	05/11 18:02:15.890	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] 2010-11-05 18:02:15 Aud path (0): AUD_PATH_NULL	192.168.2.112	05/11 18:02:15.890	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Send SIP message: 487 To 217.0.16.90:5060, sip_handle: 0x0051F8EA	192.168.2.112	05/11 18:02:15.890	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sip_len: 389, sip_handle: 0x0051F8EA, SIP/2.0 487 Request Cancelled  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  From: <sip:[email protected]	192.168.2.112	05/11 18:02:15.890	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] sending notifies from sig remote_cancel	192.168.2.112	05/11 18:02:15.906	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIPReceive(395, Account3): ACK sip:[email protected]:5064;transport=udp SIP/2.0  Via: SIP/2.0/UDP 217.0.16.90:5060;branch=z9hG4bK06af8f087f61e833dc571222ed013dba.9e0a462d  Max-Forwards: 	192.168.2.112	05/11 18:02:15.937	
<14>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] Received SIP message: 3	192.168.2.112	05/11 18:02:15.937	
<15>GS_LOG: [00:0B:82:24:AB:2C][000][9620000804A][01020403] SIP dialog not matched	192.168.2.112	05/11 18:02:15.953
 
Um antworten zu können musst du eingeloggt sein.

Zurzeit aktive Besucher

Gesamt: 522 (Mitglieder: 3, Gäste: 519)

Neueste Beiträge

Statistik des Forums

Themen
246,295
Beiträge
2,249,593
Mitglieder
373,893
Neuestes Mitglied
Kukkatto
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.
Ihr E-Mail-Adresse verifizieren

Ihr E-Mail-Adresse verifizieren

Wir haben Ihnen eine E-Mail geschickt. Klicken Sie auf die Schaltfläche im E-Mail-Text, um Ihre E-Mail-Adresse zu verifizieren – (Können Sie diese nicht finden können, dann überprüfen Sie Ihren Spam-Ordner).

IPPF im Überblick

Neueste Beiträge

Direktlinks Telefonanlage

Website-Sponsoren

3CX sponsor
KONTAKTIEREN SIE UNS BEI INTERESSE
| Style by ThemeHouse
XenPorta 2 PRO © Jason Axelrod of 8WAYRUN
Oben Unten
Zurück