Custom Search
VoIP General
VoIP News
VoIP Provider
VoIP Hardware
VoIP Software
VoIP Technology
Havn't found what you want?? TRY GOOGLE SEARCH:
VoIP News
VoIP Provider
VoIP Hardware
VoIP Software
VoIP Technology
Havn't found what you want?? TRY GOOGLE SEARCH:
Custom Search
SPA-1001 call signaling2010-12-30 | |
|
Nextiva is a cloud based VoIP phone system, hosting lots of small and medium sized businesses nationwide. the provides UNLIMITED business calling for only $19.95 a month!! Click here for the detail about this promotion!!
Hello of people, I needs assistance.
I have a Sipura SPA-1001 with account with Web.de. The following scenario: If I call somewhere and it off lift after 8 call tones none (e.g. Granny does not come so fast to the telephone ran) the call procedure is broken off. Why? Can I there which to change it longer with the other one bimmelt? 
Hello, I have the same problem. Also times would interest me whether it in it a solution gives… Sometimes that is rather nervig… Times my signature provided. Hopefully it fits in such a way.
No a solution has ready.  Property times the manuals durchforstet. Is however endless. Do not get ahead simply. Property at the configuration already tinkered abere without success. 
Try in regionally the attitudes with “ring-bake clay/tone” the star, which stands for clammy ones after semicolon and before that, by the number of seconds, which the procedure is to take to replace. White not whether goes, but with dial clay/tone, ring Patterns etc. the number before that is clammy one the duration in seconds. Let us know whether which brings. However unfortunately nothing brought thanks for that. If I irgenwo call goes the call clay/tone 6-7mal or so approx. 30 seconds. raus and then Schluss.Und is some does not create it not so fast to the telephone.
Property times the LINE 2 with T-Online VoiP (much too expensive!!!  ) furnished. So that also the same problem is after ca.7 calls conclusion. Thus it is to attitudes of the SPA-1001 probably because of that.
Problematic it is actually only that you both seem to be the only one with this problem. Check times in the Syslog, who terminates the call (SPA or receiving station): http://www.ippf.tk/forum/viewtopic.php?t=537 If need be Factory RESETs. Here times hopefully log komplettet Code: 2005-05-12 22:14: 34 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 34 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 34 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 34 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 34 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 Calling: nummer@sip.web.de: 0 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] AUD ALLOC CALL (port=16436) 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] RTP Rx UP 2005-05-12 22:14: 35 Local3.Debug 192.168.2.20 RSE_DEBUG: reference domain: sip.web.de 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 “INVITE sip: nummer@sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-fdfca11e< 013><,010> From: name <sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 101 INVITE< 013><,010> max Forwards: 70<,013><,010> Contact: name< sip: name@ 192.168.2.20: 5060>< 013><,010> Expires: 240<,013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 428<,013><,010> Allow: ACK, BYE, cancel, info., INVITE, NOTIFY, OPTION, REFER< 013><,010> Supported: x-sipura< 013><,010> content type: application/sdp< 013><,010><,013><,010> v=0< 013><,010> o= 8499546 8499546 IN IP4 192.168.2.20< 013><,010> s=< 013><,010> c=IN IP4 192.168.2.20< 013><,010> t=0 0<,013><,010> m=audio 16436 RTP/AVP 0 2 4 8 18 96 97 98 100,101<,013><,010> a=rtpmap: 0 PCMU/8000< 013><,010> a=rtpmap: 2 G726-32/8000< 013><,010> a=rtpmap: 4 G723/8000< 013><,010> a=rtpmap: 8 PCMA/8000< 013><,010> a=rtpmap: 18 G729a/8000< 013><,010> a=rtpmap: 96 G726-40/8000< 013><,010> a=rtpmap: 97 G726-24/8000< 013><,010> a=rtpmap: 98 G726-16/8000< 013><,010> a=rtpmap: 100 NSE/8000< 013><,010> a=rtpmap: 101 telephone-event/8000< 013><,010> a=fmtp: 101 0-15< 013><,010> a=ptime: 30<,013><,010> a=sendrecv " 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 “SIP/2.0 407 Proxy Authentication Required< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-fdfca11e; rport=58744; received= 84.150.182.200< 013><,010> From: name <sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=f43d8ce4e4130f38b15965d9884f209e.7fa4< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 101 INVITE< 013><,010> Proxy Authenticate: Digest realm= "" web.de "", nonce= "" 4283ba29025d9fe34496c43db5145535876b9d68 ""< 013><,010> servers: Sip express rout (0.8.14 (i386/linux))<013><,010> content length: 0<,013><,010> warning: 392 sip ha.web.de: 5060 "" Noisy feedback tells: pid=26379 req_src_ip= 84.150.182.200 req_src_port=58744 in_uri=sip: nummer@sip.web.de out_uri=sip: nummer@sip.web.de via_cnt==1 """ 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 ACK sip: nummer@sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-fdfca11e< 013><,010> From: name <sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=f43d8ce4e4130f38b15965d9884f209e.7fa4< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 101 ACK< 013><,010> max Forwards: 70<,013><,010> Contact: name< sip: name@ 192.168.2.20: 5060>< 013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 0 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local3.Debug 192.168.2.20 RSE_DEBUG: reference domain: sip.web.de 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 “INVITE sip: nummer@sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-acf78612< 013><,010> From: name <sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 INVITE< 013><,010> max Forwards: 70<,013><,010> Proxy Authorization: Digest username= "" name "", realm= "" web.de "", nonce= "" 4283ba29025d9fe34496c43db5145535876b9d68 "", uri= "" sip: nummer@sip.web.de "", algorithm=MD5, response= "" f6e4b324404b4c05aef073cc29abdd60 ""< 013><,010> Contact: name <sip: name@ 192.168.2.20: 5060>< 013><,010> Expires: 240<,013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 428<,013><,010> Allow: ACK, BYE, cancel, info., INVITE, NOTIFY, OPTION, REFER< 013><,010> Supported: x-sipura< 013><,010> content type: application/sdp< 013><,010><,013><,010> v=0< 013><,010> o= 8499546 8499546 IN IP4 192.168.2.20< 013><,010> s=< 013><,010> c=IN IP4 192.168.2.20< 013><,010> t=0 0<,013><,010> m=audio 16436 RTP/AVP 0 2 4 8 18 96 97 98 100,101<,013><,010> a=rtpmap: 0 PCMU/8000< 013><,010> a=rtpmap: 2 G726-32/8000< 013><,010> a=rtpmap: 4 G723/8000< 013><,010> a=rtpmap: 8 PCMA/8000< 013><,010> a=rtpmap: 18 G729a/8000< 013><,010> a=rtpmap: 96 G726-40/8000< 013><,010> a=rtpmap: 97 G726-24/8000< 013><,010> a=rtpmap: 98 G726-16/8000< 013><,010> a=rtpmap: 100 NSE/8000< 013><,010> a=rtpmap: 101 telephone-event/8000< 013><,010> a=fmtp: 101 0-15< 013><,010> a=ptime: 30<,013><,010> a=sendrecv " 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 “SIP/2.0 100 trying -- your call is important tons of US< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-acf78612; rport=58744; received= 84.150.182.200< 013><,010> From: name <sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 INVITE< of 013><,010> servers: Sip express rout (0.8.14 (i386/linux))<013><,010> content length: 0<,013><,010> warning: 392 sip ha.web.de: 5060 "" Noisy feedback tells: pid=26378 req_src_ip= 84.150.182.200 req_src_port=58744 in_uri=sip: nummer@sip.web.de out_uri=sip: nummer@sip.web.de via_cnt==1 """ 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 35 Local7.Debug 192.168.2.20 “SIP/2.0 183 session progress< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; received= 84.150.182.200; branch=z9hG4bK-acf78612< 013><,010> From: name< sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=as50c2191f< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 INVITE< 013><,010> user agent: Asterisk PBX< 013><,010> Allow: INVITE, ACK, cancel, OPTION, BYE, REFER< 013><,010> Contact: <sip: nummer@ 217.72.200.72: 5060>< 013><,010> content type: application/sdp< 013><,010> content length: 316<,013><,010><,013><,010> v=0< 013><,010> o=root 2539 2539 IN IP4 217.72.200.72< 013><,010> s=session< 013><,010> c=IN IP4 217.72.200.72< 013><,010> t=0 0<,013><,010> m=audio 10942 RTP/AVP 8 0 2 3 97 101<,013><,010> a=rtpmap: 8 PCMA/8000< 013><,010> a=rtpmap: 0 PCMU/8000< 013><,010> a=rtpmap: 2 G726-32/8000< 013><,010> a=rtpmap: 3 GSM/8000< 013><,010> a=rtpmap: 97 iLBC/8000< 013><,010> a=rtpmap: 101 telephone-event/8000< 013><,010> a=fmtp: 101 0-16< 013><,010> a=silenceSupp: off -- --“ 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 CC: Call progress 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] ENC INIT 0 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] RTP Tx UP (pt=0> d948c848: 10942) 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] RTCP Tx UP 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] RTP Rx 1st PKT @16436 (2) 2005-05-12 22:14: 35 Local2.Debug 192.168.2.20 [0: 0] DEK INIT 0 2005-05-12 22:14: 37 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 37 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 37 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 37 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 37 Local2.Debug 192.168.2.20 CC: Call progress 2005-05-12 22:14: 37 Local2.Debug 192.168.2.20 [0: 0] RTP Tx DN 2005-05-12 22:14: 37 Local2.Debug 192.168.2.20 [0: 0] ENC INIT 0 2005-05-12 22:14: 37 Local2.Debug 192.168.2.20 [0: 0] RTP Tx UP (pt=0> d948c848: 10942) 2005-05-12 22:14: 40 Local3.Debug 192.168.2.20 RSE_DEBUG: reference domain: sip.web.de 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:14: 40 Local7.Debug 192.168.2.20 “REGISTERS sip: sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-715c709< 013><,010> From: name< sip: name@sip.web.de>; tag=380b3615c216ebb6o0< 013><,010> tons: name< sip: name@sip.web.de>< 013><,010> call ID: 4746cd1-9cd2c42a@ 192.168.2.20< 013><,010> CSeq: 1707 REGISTERS< 013><,010> max Forwards: 70<,013><,010> Authorization: Digest username= "" name "", realm= "" web.de "", nonce= "" 4283b9466d867de8f986a124402d3d1d5e93b763 "", uri= "" sip: sip.web.de "", algorithm=MD5, response= "" 84e96b7b4ed29f063003111e8175f891 ""< 013><,010> Contact: name <sip: name@ 192.168.2.20: 5060>; expires=60< 013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 0<,013><,010> Allow: ACK, BYE, cancel, info., INVITE, NOTIFY, OPTION, REFER< 013><,010> Supported: x-sipura " 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 40 Local7.Debug 192.168.2.20 “SIP/2.0 200 OK ONE <013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-715c709; rport=58744; received= 84.150.182.200< 013><,010> From: name< sip: name@sip.web.de>; tag=380b3615c216ebb6o0< 013><,010> tons: name< sip: name@sip.web.de>; tag=f43d8ce4e4130f38b15965d9884f209e.2dd6< 013><,010> call ID: 4746cd1-9cd2c42a@ 192.168.2.20< 013><,010> CSeq: 1707 REGISTERS< of 013><,010> servers: Sip express rout (0.8.14 (i386/linux))<013><,010> content length: 0<,013><,010> warning: 392 sip ha.web.de: 5060 "" Noisy feedback tells: pid=26387 req_src_ip= 84.150.182.200 req_src_port=58744 in_uri=sip: sip.web.de out_uri=sip: sip.web.de via_cnt==1 """ 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 40 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 40 Local3.Debug 192.168.2.20 [0] RegOK. NEXT-move in 59 (1) 2005-05-12 22:14: 44 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 44 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 44 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 44 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 44 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:14: 45 Local3.Debug 192.168.2.20 “RSE_DEBUG: unref domain, sip.web.de " 2005-05-12 22:14: 47 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 47 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 47 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 47 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 47 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:14: 51 Local2.Debug 192.168.2.20 [0: 0] LAT-- 7 (2) 2005-05-12 22:14: 54 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 54 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 54 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 54 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 54 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:14: 57 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 57 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:14: 57 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 57 Local0.Info 192.168.2.20 <010> 2005-05-12 22:14: 57 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:14: 59 Local2.Debug 192.168.2.20 [0: 0] LAT-- 6 (2) 2005-05-12 22:15: 04 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 04 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 04 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 04 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 04 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:15: 07 Local3.Debug 192.168.2.20 “RSE_DEBUG: unref domain, sip.web.de " 2005-05-12 22:15: 07 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 07 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 07 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 07 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 07 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:15: 14 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 14 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 14 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 14 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 14 Local2.Debug 192.168.2.20 Disk pool of broadcasting corporations RSP w/o trnsac 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 15 Local7.Debug 192.168.2.20 “SIP/2.0 403 Forbidden< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; received= 84.150.182.200; branch=z9hG4bK-acf78612< 013><,010> From: name< sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=as50c2191f< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 INVITE< 013><,010> user agent: Asterisk PBX< 013><,010> Allow: INVITE, ACK, cancel, OPTION, BYE, REFER< 013><,010> Contact: <sip: nummer@ 217.72.200.72: 5060>< 013><,010> content length: 0 " 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:15: 15 Local7.Debug 192.168.2.20 “ACK sip: nummer@sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-acf78612< 013><,010> From: name< sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=as50c2191f< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 ACK< 013><,010> max Forwards: 70<,013><,010> Proxy Authorization: Digest username= "" name "", realm= "" web.de "", nonce= "" 4283ba29025d9fe34496c43db5145535876b9d68 "", uri= "" sip: nummer@sip.web.de "", algorithm=MD5, response= "" 77495da4782a8ea7dd912a5c4187aea4 ""< 013><,010> Contact: name< sip: name@ 192.168.2.20: 5060>< 013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 0 " 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 15 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 15 Local2.Debug 192.168.2.20 [0: 0] AUD Rel call 2005-05-12 22:15: 15 Local2.Debug 192.168.2.20 CC: Failed 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 [0: 5060]<< 217.72.200.89: 5060 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 [0: 5060] -> 217.72.200.89: 5060 2005-05-12 22:15: 17 Local7.Debug 192.168.214.20 “ACK sip: nummer@sip.web.de SIP/2.0< 013><,010> via: SIP/2.0/UDP 192.168.2.20: 5060; branch=z9hG4bK-acf78612< 013><,010> From: name< sip: name@sip.web.de>; tag=8d861afe7eed5f6o0< 013><,010> tons: <sip: nummer@sip.web.de>; tag=as50c2191f< 013><,010> call ID: 3dfea2e3-15706652@ 192.168.2.20< 013><,010> CSeq: 102 ACK< 013><,010> max Forwards: 70<,013><,010> Proxy Authorization: Digest username= "" name "", realm= "" web.de "", nonce= "" 4283ba29025d9fe34496c43db5145535876b9d68 "", uri= "" sip: nummer@sip.web.de "", algorithm=MD5, response= "" 77495da4782a8ea7dd912a5c4187aea4 ""< 013><,010> Contact: name< sip: name@ 192.168.2.20: 5060>< 013><,010> user agent: Sipura/SPA1001-2.0.13 (SEg)< 013><,010> content length: 0 " 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 <010> 2005-05-12 22:15: 17 Local0.Info 192.168.2.20 <010>Only with the log do not get ahead I
First times caution, if one postet a Mitschnitt, one should before all numbers and account name rauslschen! I made times even. Otherwise the following: You register yourself every 59 seconds again, could be somewhat much, happened during ringing, should not however not the problem be (could take nevertheless higher values). Then comes however after 40 seconds, thus to that 8. Ring a Forbidden (403) of Web.de. Property straight times account and it is the same problem means excavated, is thus because of Web.de. There nothing else probably remains for you to take as another Provider. Thanks for your info.  . Will times nen other Provider to search.  Genuinly top class this forum!!!!! Oh which Provider is so actually price/achievement-moderately for recommending (simply announce and telephone without basic charges)? Hello, I tested the problem times with ours, ring it more frequently than 8 times. Unfortunately our service actually only next week starts, if necessary I could de-energise you already today. With interest you visit yourselves a tariff http://http://www.ip-phone-forum.de/showthread.php/www.interfoni.de out and write simply email with your address and email an address down Interfoni.de voip (voice over IP) De-energising within 12 hours. HP. how it me seems is we at present the most favorable offerer without basic charges! Many greetings Franc Meyer Interfoni.de voip (voice over IP) |
