[test-results] [Bamboo] Asterisk > Asterisk Build > #1813 has FAILED. Change made by Joshua Colp and Mark Michelson.

[Bamboo]

-----------------------------------------------------------------------
Asterisk > Asterisk Build > #1813 failed.
-----------------------------------------------------------------------
Code has been updated by Joshua Colp, Mark Michelson.
1/2 jobs failed, no tests found.

https://bamboo.asterisk.org/bamboo/browse/AST-ATRUNKBUILD-1813/

---------------------
Currently Responsible
---------------------

foobar  (Automatically assigned)



--------------
Failing Jobs
--------------
  - Basic Build (Basic Build): No tests found.



--------------
Code Changes
--------------
Joshua Colp (8159bb663ed28ecd75a599702c3053a20aee4c1f):

>pjsip: Add test for outbound registration with line support.
>This test sends an outbound registration to a SIPP scenario which,
>upon completion, sends a call back into Asterisk using the Contact
>of the REGISTER. As this Contact contains a line parameter the
>res_pjsip_outbound_registration module associates it with the outbound
>registration and identifies it as the configured endpoint.
>
>ASTERISK-24949
>Reported by: Joshua Colp
>
>Change-Id: I4c80a969e4f29d49e83a03b3b0fed395d6ce2421

Mark Michelson (4475945a24697b17b2747b40d4b2811f4ba73723):

>Merge "chan_dahdi: Add the chan_dahdi.conf force_restart_unavailable_chans option."

Richard Mudgett (03c51cf525f449b8a70db5cf7aeefd96636fe6f7):

>chan_dahdi: Add the chan_dahdi.conf force_restart_unavailable_chans option.
>Some telco switches occasionally ignore ISDN RESTART requests.  The fix
>for ASTERISK-19608 added an escape clause for B channels in the restarting
>state if the telco ignores a RESTART request.  If the telco fails to
>acknowledge the RESTART then Asterisk will assume the telco acknowledged
>the RESTART on the second call attempt requesting the B channel by the
>telco.  The escape clause is good for dealing with RESTART requests in
>general but it does cause the next call for the restarting B channel to be
>rejected if the telco insists the call must go on that B channel.
>
>chan_dahdi doesn't really need to issue a RESTART request in response to
>receiving a cause 44 (Requested channel not available) code.  Sending the
>RESTART in such a situation is not required (nor prohibited) by the
>standards.  I think chan_dahdi does this for historical reasons to deal
>with buggy peers to get channels unstuck in a similar fashion as the
>chan_dahdi.conf resetinterval option.
>
>* Add the chan_dahdi.conf force_restart_unavailable_chans compatability
>option that when disabled will prevent chan_dahdi from trying to RESTART
>the channel in response to a cause 44 code.
>
>ASTERISK-25034 #close
>Reported by: Richard Mudgett
>
>Change-Id: Ib8b17a438799920f4a2038826ff99a1884042f65



--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20150430/8bd4ecae/attachment-0001.html>