[asterisk-users] Asterisk put call on hold when receive 183 Session Progress with media address 0.0.0.0 in SDP

[Rafael dos Santos Saraiva]

The problem the 183 is received with mode sendonly and playbacks an audio,
so when the destination playbacks audio, the origin was put on hold.

     |                               |
     |          INVITE               |
     |------------------------------>|
     | 183 Session Progress/SDP      |
     |<------------------------------|
     |          RTP one way          |
     |<------------------------------|
     |            BYE                |
     |<------------------------------|
     |                               |


This method is used by telco to playback message to not found user.




2017-10-06 3:25 GMT-03:00 Jean Aunis <jean.aunis at prescom.fr>:

> I think it is normal, the call is placed on hold as soon as the remote
> media address is null.
>
> It makes sense because when a 183 is sent, some media is supposed to be
> sent as with a 200, so placing the call on hold when no media is available
> sounds logic.
>
> Le 06/10/2017 à 03:56, Rafael dos Santos Saraiva a écrit :
>
> Hi
>
>
> Is it a normal behavior of Asterisk put a call on hold when receive a
> Session Progress with media address 0.0.0.0 in SDP? I believe the call on
> hold should be initiate with a re-invite.
>
>
> Thanks
>
> --
> Att,
> Rafael Saraiva
>
>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at: https://community.asterisk.
> org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>



-- 
Att,
Rafael Saraiva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20171006/6cfc8c51/attachment.html>