| Summary: | ASTERISK-00279: chan_h323 dies if the gatekeeper isn't available | ||
| Reporter: | thaeger (thaeger) | Labels: | |
| Date Opened: | 2003-09-16 05:23:54 | Date Closed: | 2004-09-25 02:21:15 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If the "gatekeeper" is set to a ip address of a gatekeeper, and anything goes wrong through the registration, asterisk dies. ****** ADDITIONAL INFORMATION ****** This is not usable in this case. The gatekeeper can be down on any grounds.... and the asterisk can never be started if the chan_h323 module shall be loaded. | ||
| Comments: | By: jerjer (jerjer) 2003-10-09 21:17:59 I disagree, look at the H.323 spec, if a gatekeeper is in the network it SHALL be used. Leme see what I can do about this. By: Paul Cadach (pcadach) 2003-10-13 05:27:51 May be just to unload h.323 module when gatekeeper is configured and cannot be contacted instead of crash *? By: jerjer (jerjer) 2003-11-09 12:01:11.000-0600 Instead of killing Asterisk at load, just warn about GK Registration failure. However, I can see a few potential problems with this simple fix. Mainly when u attempt to dial no Gatekeeper will be around to place your all and I am not able to test to see if Open H.323 will attempt another registration at dial. | ||