[asterisk-users] SIP registration failure stops all SIP activity
I have a problem that when one of my SIP providers has a problem the rest of my SIP extensions and trunks stop working until either the SIP provider fixes the problem or Asterisk stops trying to register to that provider. Why does this happen? A single provider having problems should not grind everything else to a halt! At this moment I either have to comment the register lines for that provider or wait until the registration times out (I have 10 attempts and 60 second delay in sip.conf). During that time all sip phones have no service and other trunk providers (SIP) are all UNREACHABLE. Is there something I can change in my sip.conf to prevent this problem? -- Telecomunicaciones Abiertas de México S.A. de C.V. Carlos Chávez Prats Director de Tecnología +52-55-91169161 ext 2001 signature.asc Description: This is a digitally signed message part -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SIP Registration Failure Logging
Try: core set verbose 4 >From the Asterisk CLI -uzzi PS: If you're not seeing any connection information, be sure to double-check the IP address is correct. Learned that lesson the hard way =\ On Sun, Jan 31, 2010 at 5:51 PM, Jim Rosenberg wrote: > Let's say I have two Asterisk boxes, A and B. I am trying to get A to do > SIP registration on B, so an extension for A can dial SIP phones covered by > B. If I examine the logs on B, if the registration succeeds, I am seeing a > notice to that effect on B. But if the registration *fails*, i'm not seeing > any message logged on B. Maybe I'm just not looking in the right place. Is > there a way to turn on logging or debugging so registration failures are > logged on the "target"? > > I'm doing something profoundly stupid, and seeing the notorious > > chan_sip.c:12009 handle_response_invite: Failed to authenticate on INVITE > > message, and trying to trace why. > > -Thanks, Jim > > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] SIP Registration Failure Logging
Let's say I have two Asterisk boxes, A and B. I am trying to get A to do SIP registration on B, so an extension for A can dial SIP phones covered by B. If I examine the logs on B, if the registration succeeds, I am seeing a notice to that effect on B. But if the registration *fails*, i'm not seeing any message logged on B. Maybe I'm just not looking in the right place. Is there a way to turn on logging or debugging so registration failures are logged on the "target"? I'm doing something profoundly stupid, and seeing the notorious chan_sip.c:12009 handle_response_invite: Failed to authenticate on INVITE message, and trying to trace why. -Thanks, Jim -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Sip registration Failure
Hi List, I am very new to asterisk. I downloaded asterisk from CVS head yesterday and compiled it in Redhat linux 9. I created a sip account for testing and configured it in the Firefly. While Firefly try to connect to the asterisk server i am getting an error as below and failing the registration. Oct 1 08:00:57 NOTICE[23415]: chan_sip.c:10646 handle_request_register: Registration from '"200" ' failed for '192.168.10.200' - Not a local SIP domain My sip configuration is as below, [general] context=default ; Default context for incoming calls bindport=5060 bindaddr=0.0.0.0 [test] type=peer secret=200 username=200 host=dynamic nat=no #disallow=all allow=all context=default Please help me to find out the problem in my configuration. Thanks in advance Rgds Anil ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] SIP Registration failure
Hi list, I'm in central-europe and signed yesterday a broadvoice account. My Asterisk box is CVS 2005-08-25. Problem I face is: "Failed to authenticate on REGISTER to '[EMAIL PROTECTED]' (Tries 2)" then "Registration for '[EMAIL PROTECTED]' timed out" and finaly "Giving up forever to register '[EMAIL PROTECTED]'" If I do keewi*CLI> sip show peers Name/username Host Dyn Nat ACL Mask Port Status broadvoice/ 147.135.20.128 255.255.255.255 5060 OK (213 ms) keewi*CLI> sip show registry Host Username Refresh State sip.broadvoice.com:5060 120 Failed In log files with sip debug I found Aug 27 16:38:09 VERBOSE[10641] logger.c: <-- SIP read from 147.135.0.128:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 83.30.64.252:5060;branch=z9hG4bK70ac947c From: "asterisk" ;tag=as0de7b82c To: ;tag=SD384v999- Call-ID: [EMAIL PROTECTED] CSeq: 102 OPTIONS Accept: application/sdp,application/broadsoft,text/plain Allow: ACK,BYE,CANCEL,INFO,INVITE,MESSAGE,OPTIONS,PRACK,REFER,REGISTER,SUBSCRIBE,NOTIFY,UPDATE Supported: 100rel Content-Length: 0 I'm registered with few others suppliers, SIP and IAX2 without any problem. Have someone an idea on what's happend? My ping time is 140 ms. Thanks for any hint. -- Daniel ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
