search for: reregistr

...is major bottleneck? qualify imho not. i'm tried set qualify=no, does not help SIP REGISTER packets? this problem persist if no calls are active after restart cpu usage slowly increase. after a ~hour is about 100% which optimalizations do you recommend for ~1500 peers scenario? (behind nat, reregistrations) --------------------------------------- Marek Cervenka =======================================

...nds a new registration message every minute! And every time my asterisk box sends a registration, it gots a sucessful response, and shows de message: "Oct 14 16:48:22 NOTICE[4090]: chan_sip.c:8742 handle_response_register: Outbound Registration: Expiry for gvt.com.br is 60 sec (Scheduling reregistration in 45 s)" I?m using asterisk-1.2.0-beta and the sip.conf parameters about registration: defaultexpirey=1200 registertimeout=1200 There is any way to make asterisk follow the 1200 seconds I?m trying to tell? Could be something happening out of my unit but at the provider network? T...

...listed my sip file below as well. Inbound calls work and I am registered. Before we go into the debug, I get this message when I reload my configs files. Mar 9 13:23:48 NOTICE[3161]: chan_sip.c:6779 handle_response: Outbound Registration: Expiry for sip.broadvoice.com is 1948 sec (Scheduling reregistration in 1933000 ms) Below is the debug: -- Executing Dial("OSS/dsp", "SIP/xxxxxxxxxx@sip.broadvoice.com|30") in new stack We're at outsideIPaddress port 14842 Answering with preferred capability 0x4 (ulaw) 12 headers, 8 lines Reliably Transmitting: INVITE sip:xxxxx...

...06c6897a0807ea21158aef1749cbe0@127.0.0.1 Expires: 3600 CSeq: 102 REGISTER Contact: <sip:s@38.115.19.11> Content-Length: 0 9 headers, 0 lines Mar 21 14:52:42 NOTICE[13089]: chan_sip.c:6797 handle_response: Outbound Registration: Expiry for sipvoiceline.net2phone.com is 3600 sec (Scheduling reregistration in 3585000 ms) Destroying call '0306c6897a0807ea21158aef1749cbe0@127.0.0.1' 11 headers, 2 lines Reliably Transmitting: NOTIFY sip:bedroom2@192.168.5.143:5061 SIP/2.0 Via: SIP/2.0/UDP 192.168.5.200:5060;branch=z9hG4bK5be6f565;rport From: "asterisk" <sip:asterisk@192.168.5.2...

Hi all, I'm having trouble with incoming IAX2 calls on 1.2.7.1 - mostly they work, but sometimes the caller just gets dead air or disconnects. IAX2 debugs show HANGUP and INVALID codes in these cases, rather than a proper RINGING transaction. My firewall is doing NAT, and changing the source port from 4569 to something else - my IAX2 provider suggested this might be a problem. Is it?

Can one server (like AMD 6000+ X2) with 2 GIG ram running asterisk 1.4 handle having 2100 wireless phones connected. All phones will not be talking at the same time only a couple will be. There may be 1 T1 card in the box. Will this work? If not how does one handle this situation. Thanks, Jerry

I'm sure this has been asked a million times before, but is there an easy wa to have Asterisk register more than one (distinct) contact binding concurrently? The goal is to have two phones register with the same credentials from different locations and consistently and reliably ring on inbound calls, irrespective of their registration intervals and so on. -- Alex Balashov Evariste Systems

...headers 0 lines) --- Scheduling destruction of SIP dialog ' 65a8d48738a00d121fc9050e4771d0b7 at 192.168.1.51' in 32000 ms (Method: REGISTER) [Dec 25 00:42:31] NOTICE[2898]: chan_sip.c:16740 handle_response_register: Outbound Registration: Expiry for sip.broadvoice.com is 30 sec (Scheduling reregistration in 23 s) REGISTER 11 headers, 0 lines Reliably Transmitting (no NAT) to 147.135.32.226:5060: REGISTER sip:sip.broadvoice.com SIP/2.0 Via: SIP/2.0/UDP 68.100.66.3:5060;branch=z9hG4bK35a02655;rport Max-Forwards: 70 From: <sip:703XXXYYYY at sip.broadvoice.com<sip%3A703XXXYYYY at sip.broad...

...;Noisy feedback tells: pid=22109 req_src_ip=82.x.x.x req_src_port=63817 in_uri=sip:sipgate.co.uk out_uri=sip:sipgate.co.uk via_cnt==1" 10 headers, 0 lines Aug 6 17:07:14 NOTICE[1493]: chan_sip.c:6814 handle_response: Outbound Registration: Expiry for sipgate.co.uk is 120 sec (Scheduling reregistration in 105000 ms) Destroying call '41b71efb79e2a9e37545e146515f007c@127.0.0.1' >From what I'm guessing it is some kind of problem with my network, any ideas what is going on and how I could solve it? Thanks. _________________________________________________________________ It...

...0c7265410ed2cff3fb69d93@sip.broadvoice.com CSeq: 108 REGISTER Contact: <sip:80171@192.168.1.108>;expires=20 Content-Length: 0 --- (8 headers 0 lines)--- Mar 21 20:56:22 NOTICE[29257]: chan_sip.c:7659 handle_response: Outbound Registration: Expiry for sip.broadvoice.com is 20 sec (Scheduling reregistration in 15999 ms) Destroying call '70a50d7620c7265410ed2cff3fb69d93@sip.broadvoice.com' <-- SIP read from 147.135.0.128:5060: BYE sip:310xxxMyBV@192.168.1.108 SIP/2.0 Via: SIP/2.0/UDP 147.135.0.128:5060;branch=z9hG4bK2qf87u30e8a009sk06s1.1sr From: <sip:1509xxxMyCP@sip.broadvoice.com&...

...<sip:31717110342@62.131.187.108:5060>;q=0.00;expires=120 Server: Sip EXpress router (0.8.14-5 (i386/linux)) Content-Length: 0 ? ? --- (9 headers 0 lines)--- Jul 10 18:38:04 NOTICE[26004]: chan_sip.c:8266 handle_response: Outbound Registration: Expiry for budgetphone.nl is 120 sec (Scheduling reregistration in 105000 ms) Destroying call '26dfb15414601a871799536a3de1f776@127.0.0.1' server*CLI> <-- SIP read from 81.23.228.150:5060: INVITE sip:31717110342@62.131.187.108:5060 SIP/2.0 Max-Forwards: 10 Record-Route: <sip:31717110342@81.23.228.150;ftag=as47419911;lr=on> Via: SIP/2.0/...

Hi All, I am new to this community and just subscribed. We have Asterisk running in production but I could not find out in documentation as well as web that how many maximum number of registrations an Asterisk Server can support. We have it on a 1.4 GHz Processor, 2 GB RAM and 40 GB HDD IBM Server. Please suggest urgently. Thanks. Best Regards, ------------------------------------- Abid

I lost my internet connection today for a short time. During that time 1.2.12.1 stopped talking to my phones. Asterisk was still working as I got 2 voicemails. I have TDM analog cards for incoming calls. Anyway my cisco phones had X's (lost registration) and my uniden phones said "Registration error". Why would phones loose registration to asterisk when the internet connection

...rs 0 lines) --- Scheduling destruction of SIP dialog '7c356bca35c9e62f6c90c3287466e70a at sip.broadvoice.com' in 32000 ms (Method: REGISTER) [Mar 16 15:52:39] NOTICE[27524]: chan_sip.c:14949 handle_response_register: Outbound Registration: Expiry for sip.broadvoice.com is 30 sec (Scheduling reregistration in 23 s) net-xero*CLI> <--- SIP read from UDP://147.135.0.128:5060 ---> INVITE sip:<my Broadvoice #>@<servers IP>:5060 SIP/2.0 Call-ID: 660240-66 at 147.135.0.128 CSeq: 1 INVITE From: "Toronto ON"<sip:<my cell #>@147.135.0.128;user=phone>;tag=ikmn To:...

...ip:31717110342@62.131.187.108:5060>;q=0.00;expires=120 Server: Sip EXpress router (0.8.14-5 (i386/linux)) Content-Length: 0 --- (9 headers 0 lines)--- Jul 10 18:38:04 NOTICE[26004]: chan_sip.c:8266 handle_response: Outbound Registration: Expiry for budgetphone.nl is 120 sec (Scheduling reregistration in 105000 ms) Destroying call '26dfb15414601a871799536a3de1f776@127.0.0.1' server*CLI> <-- SIP read from 81.23.228.150:5060: INVITE sip:31717110342@62.131.187.108:5060 SIP/2.0 Max-Forwards: 10 Record-Route: <sip:31717110342@81.23.228.150;ftag=as47419911;lr=on> Via: S...

....48.217.39:5060>;expires=55 Content-Length: 0 <-------------> [Mar 23 19:25:29] VERBOSE[4067] chan_sip.c: [Mar 23 19:25:29] --- (8 headers 0 lines) --- [Mar 23 19:25:29] NOTICE[4067] chan_sip.c: Outbound Registration: Expiry for nat5.babytel.ca is 55 sec (Scheduling reregistration in 40 s) [Mar 23 19:25:29] VERBOSE[4067] chan_sip.c: [Mar 23 19:25:29] Really destroying SIP dialog '5e070a0021f200c72308ddad6fe2521c at 192.168.0.99' Method: REGISTER [Mar 23 19:25:44] VERBOSE[4003] asterisk.c: [Mar 23 19:25:44] -- Remote UNIX connection [M...

...7979] logger.c: --- (10 headers 0 lines)--- Feb 9 20:07:09 VERBOSE[27979] logger.c: Scheduling destruction of call '0c7451d45c6d9f7d58f32e7255ddb2c3@192.168.0.2' in 32000 ms Feb 9 20:07:09 NOTICE[27979] chan_sip.c: Outbound Registration: Expiry for sip001.mitacs.com is 120 sec (Scheduling reregistration in 105 s) Feb 9 20:07:26 VERBOSE[27979] logger.c: <-- SIP read from 213.185.164.123:5060: INVITE sip:43720755555@85.125.152.162:5060 SIP/2.0 Record-Route: <sip:213.185.164.123;ftag=as4217aa4d;lr> Via: SIP/2.0/UDP 213.185.164.123;branch=z9hG4bK70a3.0dcf83b3.1 Via: SIP/2.0/UDP 213.185....

...; +} + +/* + * When a guest leaves hibernation, the device driver state is out of sync + * with the device state, since the driver state has doorbells registered + * that aren't known to the device. This function takes care of + * reregistering any doorbells. In case an error occurs during + * reregistration (this is highly unlikely since 1) it succeeded the first + * time 2) the device driver is the only source of doorbell registrations), + * we simply log the error. The doorbell can still be destroyed using + * VMCIDoorbell_Destroy. + */ +void vmci_dbell_hibernate(bool enterHibernate) +{ +...

...; +} + +/* + * When a guest leaves hibernation, the device driver state is out of sync + * with the device state, since the driver state has doorbells registered + * that aren't known to the device. This function takes care of + * reregistering any doorbells. In case an error occurs during + * reregistration (this is highly unlikely since 1) it succeeded the first + * time 2) the device driver is the only source of doorbell registrations), + * we simply log the error. The doorbell can still be destroyed using + * VMCIDoorbell_Destroy. + */ +void vmci_dbell_hibernate(bool enterHibernate) +{ +...

...--- [Jan 29 19:12:53] NOTICE[19010]: chan_sip.c:8869 sip_reregister: -- Re-registration for 6087294353 at sip.broadvoice.com@sip.broadvoice.com [Jan 29 19:12:53] NOTICE[19010]: chan_sip.c:14782 handle_response_register: Outbound Registration: Expiry for sip.broadvoice.com is 30 sec (Scheduling reregistration in 23 s) Retransmitting #4 (NAT) to 10.7.10.51:5060: NOTIFY sip:5878 at 10.7.10.51:5060 SIP/2.0 Via: SIP/2.0/UDP 10.7.10.1:5060;branch=z9hG4bK23e5b645;rport Max-Forwards: 70 From: "5253" <sip:5253 at 10.7.10.1>;tag=as05a48c1a To: <sip:5878 at 10.7.10.51:5060>;tag=69441784...