27798 Commits (81ea80b74ce1ae35eb5b377a825948c27ef65b45)

 

All Branches   

Search

Author	SHA1	Message	Date
Joshua Colp	81ea80b74c	res_pjsip_exten_state: Add config support for exten state publishers. ... This change adds the ability to configure outbound publishing of extension state. Right now stuff is merely set up to store the configuration and to register a global extension state callback. The act of constructing the body and sending is not yet complete. Configurable elements right now are a regex for filtering the context, a regex for filtering the extension, and the body type to publish. ASTERISK-25922 #close Change-Id: Ia7e630136dfc355073c1cadff8ad394a08523d78	9 years ago
Joshua Colp	8ae69cffef	app_queue: Fix crash when unloading module. ... When unloading the app_queue module the members in each queue are destroyed and as part of this they are removed from the pending members container. Unfortunately a crash would occur as the container was destroyed before the members were removed. This change tweaks ordering so the container destruction occurs after the members are destroyed. ASTERISK-16115 Change-Id: I48c728668c55aee3d05b751a5d450fb57e87f44b	9 years ago
Joshua Colp	09d588dc2f	Merge changes from topic 'system_stress_patches' ... * changes: test_message.c: Wait longer in case dialplan also processes the test message. Manager: Short circuit AMI message processing. manager.c: Eliminate most RAII_VAR usage.	9 years ago
zuul	0f29785101	Merge "manager_channels.c: Fix allocation failure crash."	9 years ago
zuul	811e24f595	Merge "Bridge system: Fix memory leaks and double frees on impart failure."	9 years ago
zuul	807a765cfb	Merge "bridge_softmix.c: Fix crash if channel fails to join mixing tech."	9 years ago
Joshua Colp	456600a641	Merge "app_queue: queue members can receive multiple calls"	9 years ago
DarkS	f99ec857c8	Fix case sensitive actions in AMI QueueSummary and QueueStatus ... ASTERISK-25954 #close Reported by: Javier Acosta Change-Id: I00be83d45cc7e8385de2523012bd196aafeeb256 (cherry picked from commit c0688a6398)	9 years ago
Kevin Harwell	30ab21d5fa	app_queue: queue members can receive multiple calls ... It was possible for a queue member that is a member of at least 2 or more queues to receive mulitiple calls at the same time. This happened because of a race between when a member was being rung and when the device state notified the other queue(s) member object of the state change. This patch makes it so when a queue member is being rung it gets added to a global pool of queue members. If that same member is tried again, e.g. from another queue, and it is found to already exist in the pending member container then it will not ring that member. ASTERISK-16115 #close Change-Id: I546dd474776d158c2b6be44205353dee5bac7e48	9 years ago
George Joseph	99fcf2a791	res_agi: Prevent run_agi from eating frames it shouldn't ... The run_agi function is eating control frames when it shouldn't be. This is causing issues when an AGI is run from CONNECTED_LINE_SEND_SUB in a blond transfer. Alice calls Bob. Bob attended transfers to Charlie but hangs up before Charlie answers. Alice gets the COLP UPDATE indicating Charlie but Charlie never gets an UPDATE and is left thinking he's connected to Bob. In this case, when CONNECTED_LINE_SEND_SUB runs on Alice's channel and it calls an AGI, the extra eaten frames prevent CONNECTED_LINE_SEND_SUB from running on Charlie's channel. The fix was to accumulate deferrable frames in the "forever" loop instead of dropping them, and re-queue them just before running the actual agi command or exiting. ASTERISK-25951 #close Change-Id: I0f4bbfd72fc1126c2aaba41da3233a33d0433645	9 years ago
Joshua Colp	7f8d83fef4	Merge "func_odbc: Use one connection per DSN."	9 years ago
zuul	0bd3444654	Merge "Remove reference to non-existent sip.conf option"	9 years ago
zuul	ac50fdecdb	Merge "res_stasis: Handle re-enter stasis bridge with swap channel."	9 years ago
zuul	1df086f821	Merge "bridge: Hold off more than one imparting channel at a time."	9 years ago
Richard Mudgett	757ec6172b	test_message.c: Wait longer in case dialplan also processes the test message. ... Bumped the wait from 1 second to 5 seconds. The test message was hitting my default call handler and failing the test because it took longer. Change-Id: I3a03737f25e92983de00548fcc7bbc50dd7544ba	9 years ago
Richard Mudgett	b3cc74fda9	manager_channels.c: Fix allocation failure crash. ... An earlier allocation failure failed to create a channel snapshot for the AMI HangupRequest/SoftHangupRequest event which resulted in a crash in channel_hangup_request_cb(). Where the stasis message gets generated cannot tell if the NULL snapshot returned was because of an allocation failure or the channel was a dummy channel. * Made channel_hangup_request_cb() check if the channel blob has a snapshot and exit if it doesn't. * Eliminated the RAII_VAR usage in channel_hangup_request_cb(). Change-Id: I0b6a1c4e95cbb7d80b2a7054c6eadecc169dfd24	9 years ago
Richard Mudgett	a63656b419	Bridge system: Fix memory leaks and double frees on impart failure. ... You cannot reference the passed in features struct after calling ast_bridge_impart(). Even if the call fails. Change-Id: I902b88ba0d5d39520e670fb635078a367268ea21	9 years ago
Richard Mudgett	71dfa35540	bridge_softmix.c: Fix crash if channel fails to join mixing tech. ... softmix_bridge_join() failed because of an allocation failure. To address this, the softmix bridge technology now checks if the channel failed to join softmix successfully. In addition, the bridge now begins the process of kicking the channel out of the bridge so we don't have channels partially in the bridge for very long. * Fix the test_channel_feature_hooks.c unit tests. The test channel must have a valid codec to join the simple_bridge technology. This patch makes joining a bridge more strict by not allowing partially joined channels to remain in the bridge. Change-Id: I97e2ade6a2bcd1214f24fb839fda948825b61a2b	9 years ago
Richard Mudgett	06632a0d11	Manager: Short circuit AMI message processing. ... Improve AMI message processing performance if there are no consumers listening for the messages. We now skip creating the AMI event message text strings. Change-Id: I7b22fc5ec4e500d00635c1a467aa8ea68a1bb2b3	9 years ago
Richard Mudgett	6ddd856b86	manager.c: Eliminate most RAII_VAR usage. ... * Made ast_manager_event_blob_create() not allocate the ao2 event object with a lock as it is not needed. Change-Id: I8e11bfedd22c21316012e0b9dd79f5918f644b7c	9 years ago
Mark Michelson	924738e950	func_odbc: Use one connection per DSN. ... res_odbc was changed in Asterisk 13.8.0 to remove connection management, opting instead to let unixodbc maintain open connections and return those to Asterisk as requested. This was a boon for realtime, since it meant that multiple threads could potentially run parallel queries since they could each be using their own database connections. However, on the user-facing side, func_odbc, there were some inherent behaviors being relied on that no longer hold true after the change. One such reported behavior was that MySQL's LAST_INSERTED_ID() works per-connection. This means that if Asterisk uses separate connections for every database operation, whereas before it used one connection for everything, we have broken expectations and functionality. The fix provided in this patch is to make func_odbc use a single database connection per DSN. This way, user-facing database usage will have the same behavior as it did pre-13.8.0. However, realtime, which is the real workhorse of database interaction, will continue to let unixodbc manage connections. ASTERISK-25938 #close Reported by Edwin Vandamme Change-Id: Iac961fe79154c6211569afcdfec843c0c24c46dc	9 years ago
Leif Madsen	6ede210c98	Remove reference to non-existent sip.conf option ... Option was removed in commit 7f883ef495 ASTERISK-25927 #close Change-Id: I92f9b0196d9fc41d1d58354c07340c465ef1fcf8	9 years ago
Joshua Colp	57c908c7a5	Merge "res_pjsip_callerid: Clear out display name if id->name is not valid"	9 years ago
zuul	24913e1540	Merge "lock.c: Check *lt before dereferencing it"	9 years ago
zuul	b4dd374bc4	Merge "stringfields: Update extended string fields for master only."	9 years ago
Diederik de Groot	c991e5472e	lock.c: Check *lt before dereferencing it ... *lt is NULL if t->tracking == 0 ASTERISK-25948 #close Change-Id: I4a81af28f9c82a74aa82413d772a7dc8fa6f45ba	9 years ago
Richard Mudgett	6b1a632290	res_stasis: Handle re-enter stasis bridge with swap channel. ... We lose the fact that there is a swap channel if there is one. We currently wind up rejoining the stasis bridge as a normal join after the swap channel has already been kicked from the bridge. This patch preserves the swap channel so the AMI/ARI events can note that the channel joining the bridge is swapping with another channel. Another benefit to swaqpping in one operation is if there are any channels that get lonely (MOH, bridge playback, and bridge record channels). The lonely channels won't leave before the joining channel has a chance to come back in under stasis if the swap channel is the only reason the lonely channels are staying in the bridge. ASTERISK-25947 #close Reported by: Richard Mudgett ASTERISK-24649 Reported by: John Bigelow ASTERISK-24782 Reported by: John Bigelow Change-Id: If37ea508831d1fed6dbfac2f191c638fc0a850ee	9 years ago
Richard Mudgett	1c5248c383	bridge: Hold off more than one imparting channel at a time. ... An earlier patch blocked the ast_bridge_impart() call until the channel either entered the target bridge or it failed. Unfortuantely, if the target bridge is stasis and the imprted channel is not a stasis channel, stasis bounces the channel out of the bridge to come back into the bridge as a proper stasis channel. When the channel is bounced out, that released the block on ast_bridge_impart() to continue. If the impart was a result of a transfer, then it became a race to see if the swap channel would get hung up before the imparted channel could come back into the stasis bridge. If the imparted channel won then everything is fine. If the swap channel gets hung up first then the transfer will fail because the swap channel is leaving the bridge. * Allow a chain of ast_bridge_impart()'s to happen before any are unblocked to prevent the race condition described above. When the channel finally joins the bridge or completely fails to join the bridge then the ast_bridge_impart() instances are unblocked. ASTERISK-25947 Reported by: Richard Mudgett ASTERISK-24649 Reported by: John Bigelow ASTERISK-24782 Reported by: John Bigelow Change-Id: I8fef369171f295f580024ab4971e95c799d0dde1	9 years ago
zuul	cc9b72208f	Merge "Dial: Combine frame handling functions."	9 years ago
Joshua Colp	7bfa1784c1	Merge "pjproject: Add patch for removing strip of '[]' from header params"	9 years ago
George Joseph	70e860ec49	res_pjsip_callerid: Clear out display name if id->name is not valid ... When create_new_id_hdr creates a new RPID or PAI header, it starts by cloning the From header, then it overwrites the display name and uri from the channel's connected.id. If the connected.id.name wasn't valid, create_new_id_hdr was leaving the display name from the From header in the new RPID or PAI header. On an attended transfer where the originator had a caller id number set but not a display name, the re-INVITE to the final transferee had the number of the originator but the display name of the transferer. Added a check to clear out the display name in the new header if connected.id.name was invalid. ASTERISK-25942 #close Change-Id: I60b4bf7a7ece9b7425eba74151c0b4969cd2738b	9 years ago
zuul	c60f8e947f	Merge "PJSIP: Remove PJSIP parsing functions from uri length validation."	9 years ago
Joshua Colp	d95512a7dd	app_talkdetect: Make the module core supported. ... This module is used as part of testsuite tests to confirm stuff works. I'm accordingly marking it as core as it is required by those tests. Change-Id: I558e7af7679b22b8ed641d7dd37ee4ca35b11e88	9 years ago
Mark Michelson	0235a66532	PJSIP: Remove PJSIP parsing functions from uri length validation. ... The PJSIP parsing functions provide a nice concise way to check the length of a hostname in a SIP URI. The problem is that in order to use those parsing functions, it's required to use them from a thread that has registered with PJLib. On startup, when parsing AOR configuration, the permanent URI handler may not be run from a PJLib-registered thread. Specifically, this could happen when Asterisk was started in daemon mode rather than console-mode. If PJProject were compiled with assertions enabled, then this would cause Asterisk to crash on startup. The solution presented here is to do our own parsing of the contact URI in order to ensure that the hostname in the URI is not too long. The parsing does not attempt to perform a full SIP URI parse/validation, since the hostname in the URI is what is important. ASTERISK-25928 #close Reported by Joshua Colp Change-Id: Ic3d6c20ff3502507c17244a8b7e2ca761dc7fb60	9 years ago
Joshua Colp	64b03ec702	Merge "app_queue: Frequent segfaults in function can_ring_entry()"	9 years ago
Joshua Colp	d268fe527d	Merge "stasis_bridge.c: Update stasis bridge push diagnostic messages."	9 years ago
Joshua Colp	2b6764d8b9	Merge "res_pjsip_transport_management: Allow unload to occur."	9 years ago
Joshua Colp	4b798cc99a	Merge "bridge_channel.c: Ignore role setup failure in channel push."	9 years ago
Mark Michelson	b8b60135ec	res_pjsip_registrar: Fix bad memory-ness with user_agent. ... Recent changes to the PJSIP registrar resulted in tests failing due to missing AOR_CONTACT_ADDED test events. The reason for this was that the user_agent string had junk values in it, resulting in being unable to generate the event. I'm going to be honest here, I have no idea why this was happening. Here are the steps needed for the user_agent variable to get messed up: * REGISTER is received * First contact in the REGISTER results in a contact being removed * Second contact in the REGISTER results in a contact being added * The contact, AOR, expiration, and user agent all have to be passed as format parameters to the creation of a string. Any subset of those parameters would not be enough to cause the problem. Looking into what was happening, the thing that struck me as odd was that the user_agent variable was meant to be set to the value of the User-Agent SIP header in the incoming REGISTER. However, when removing a contact, the user_agent variable would be set (via ast_strdupa inside a loop) to the stored contact's user_agent. This means that the user_agent's value would be incorrect when attempting to process further contacts in the incoming REGISTER. The fix here is to use a different variable for the stored user agent when removing a contact. Correcting the behavior to be correct also means the memory usage is less weird, and the issue no longer occurs. ASTERISK-25929 #close Reported by Joshua Colp Change-Id: I7cd24c86a38dec69ebcc94150614bc25f46b8c08	9 years ago
Joshua Colp	6cfa02394f	res_pjsip_transport_management: Allow unload to occur. ... At shutdown it is possible for modules to be unloaded that wouldn't normally be unloaded. This allows the environment to be cleaned up. The res_pjsip_transport_management module did not have the unload logic in it to clean itself up causing the res_pjsip module to not get unloaded. As a result the res_pjsip monitor thread kept going processing traffic and timers when it shouldn't. Change-Id: Ic8cadee131e3b2c436a81d3ae8bb5775999ae00a	9 years ago
Richard Mudgett	6365f0018f	bridge_channel.c: Ignore role setup failure in channel push. ... We have to setup the channel roles after the bridge class push is called because the bridge class push callback may have set roles on the incoming channel. Since we have already partially pushed the channel into the bridge and reversing what we have already done could be problematic, the only thing we can do is press on to complete pushing the channel into the bridge. * Ignore any channel role setup errors after pushing the channel into a bridge. The channel may behave incorrectly in the bridge but we can no longer abort the push at this time. Change-Id: I08a97082b729052ee65cdca6bb730cf1289ede00	9 years ago
Jaco Kroon	f06ce7f90a	chan_sip: Don't verify table if rtupdate=no ... If rtupdate=no do not verify sipregs/peers table has updatable fields. ASTERISK-25934 #close Change-Id: Iaa2c53037b93daccc7e7333c40d61861847b856d	9 years ago
Joshua Colp	6fe38d60aa	Merge "Codecs: strip codec name while parsing allow/disallow options"	9 years ago
ibercom	dbb47e0a47	app_queue: Frequent segfaults in function can_ring_entry() ... ASTERISK-25888 #close Change-Id: I007a2f2dd99823e04fb5be3ff01f02b0a2956117	9 years ago
Richard Mudgett	af114edb8b	stasis_bridge.c: Update stasis bridge push diagnostic messages. ... Change-Id: I195b14994c9dcccb9452491ca20a885d2a54605a	9 years ago
Joshua Colp	f7a434fa6d	Merge "app_voicemail/IMAP: function 'save_to_folder' creates wrong folder"	9 years ago
Mark Michelson	5e64d7e7a3	Dial: Combine frame handling functions. ... There is a good amount of repetition in the two frame handling routines in the Dial API. This commit combines the two functions into one. This is in preparation for an upcoming commit that adds the ability to handle frames for a channel in a bridge. ASTERISK-25925 Reported by Mark Michelson Change-Id: Iaae2f174e3058e774cb44e10659fcdfb85345c58	9 years ago
Alexei Gradinari	a6e2ba187a	Codecs: strip codec name while parsing allow/disallow options ... Failed registration using PJSIP/Realtime if one of the codec name in allow/disallow option is wrong or contains space. This patch strip codec name. ASTERISK-25914 Change-Id: Ifdf02de94e5ddbce305640f6f0666084a3b9283d	9 years ago
Mark Michelson	be4333ddad	transport management: Register thread with PJProject. ... The scheduler thread that kills idle TCP connections was not registering with PJProject properly and causing assertions if PJProject was built in debug mode. This change registers the thread with PJProject the first time that the scheduler callback executes. AST-2016-005 Change-Id: I5f7a37e2c80726a99afe9dc2a4a69bdedf661283	9 years ago
Joshua Colp	d3e4d10f04	Merge "res_pjsip_transport_management: Kill idle TCP connections."	9 years ago