Asterisk 12 – 100rel (Prack) No 100rel Require In Responses

Home » Asterisk Users » Asterisk 12 – 100rel (Prack) No 100rel Require In Responses
Asterisk Users 3 Comments

Hi

I am trying out Asterisk 12 between two servers in order to test the 100rel (PRACK) capability. When I set the called server to send Ringing (180) and wait before answering the call it is not sending 100rel Require in the Ringing message (non provisional response) therefore the calling server does not send a PRACK.

I have the same config at both ends and if I change the 100rel field in the endpoint section in pjsip.conf on the calling server to either no; yes or

3 thoughts on - Asterisk 12 – 100rel (Prack) No 100rel Require In Responses

  • I’ve taken a look at the code and the pjsip documentation for 100rel. We appear to be using it correctly but that doesn’t mean something isn’t up. Can you provide a SIP trace showing this for a further looksee?

    Cheers,

  • I have attached two pcap traces, the file Asterisk 12 to Asterisk 12 is what happens when two Asterisk 12 servers configured as a SIP trunk call each other. At both ends in the pjsip.conf the 100rel field is set to required, you can see from the trace that the Calling server sets the 100rel Require header but the Called Server does not set this in the 180 ringing response and therefore no PRACK is sent.

    The second trace Asterisk 12 to PJSUA is one of the Asterisk 12 servers with the same configuration talking to a server running PJSUA (command line PJSIP). On this trace you can see that PJSUA sets the 100rel Require in the 180 ringing response and therefore the Asterisk 12 server sends a PRACK message, This call does not complete as I have to manually enter commands on PJSUA and once I send a 180 I cannot then send a 200 OK.

    It seems therefore that Asterisk 12 is operating correctly when making calls with 100rel but is not responding correctly on incoming calls.

  • Greetings,

    JULIAN RUSSELL wrote:

    Thanks for the traces and further clarification/description! I was able to reproduce and isolate the problem. I’ve fixed it in the 12 branch and trunk.

    Cheers,