Emia

Feature asterisk18

1

Hi, I would like to contribute to project. ChannelUserEvent -> better to post process custom message if client is interested. Websocket chan - connection state needs to be monitored, I...

Dialogs support

1

Example or some wrapper for handling dialogs

Currently only due to passing options we return error on building client or server handle. Instead doing this, we need to be explicit in passing options, and therefore remove need...

To be more like std http package, lot of current structures under `sipgo` are actually more belonging sip stack. There are pros and cons to this move Pros: - Could...

Currently dialog INVITE caller is required to do digest auth if required. This could be part of dialog invite as Options parameeter same as answer

After merging this https://github.com/emiago/sipgo/pull/68 there is some duplication code for supporting digest auth on dialog answer

SIP parser torture tests to be added. More we add the better.

Define a maximum message size and avoid useless parsing

2

TCP/UDP could be larger message size which may lead lot of bad parsing and therefore processing Original comment suggestion https://github.com/emiago/sipgo/pull/36#issuecomment-1688888984

Support setting headers like Allow, Supported

2

more related on this PR #140 We could potentially have this headers or behavior part of client or server. Ex server could detect what methods are supported and if caller...