Asterisk Hint 'InUser&Ringing' Fails to Send Correct SIP NOTIFY State

Asterisk Asterisk SIP
1

Scenario:

A, B, C, and D are part of the same PABX. D has subscribed to B using the BLF feature of the phone.

  • A calls B, and the BLF status shows ringing (SIP NOTIFY <early>).
  • B picks up the call, and the SIP NOTIFY packet changes to <confirmed>, with the BLF status switching to talking.
  • Later, C calls B. Using the Asterisk CLI command core show hints, it shows that B is in the state “InUser&Ringing”. However, the corresponding SIP NOTIFY packet sent is still <confirmed>.

I tried adding notify_early_inuse_ringing to the pjsip.conf for B, but nothing changed.

2

You should show the actual SIP traffic, and provide the actual configuration.

3

I had a look at the sip notify rfc and it seems that a single dialog is created between a subscriber and the observed. Status updates provoked by Hints are then send to the subscriber via SIP NOTIFY. But it seems that the dialog states are not are complex as the hint states used by asterisk ?

4

If you want to see the logic, here it is:

5

It would be this case :

case (AST_EXTENSION_INUSE | AST_EXTENSION_RINGING):
		if (notify_early_inuse_ringing) {
			*statestring = "early";
		} else {
			*statestring = "confirmed";
		}
		*local_state = NOTIFY_INUSE;
		*pidfstate = "on-the-phone";
		*pidfnote = "Ringing";
		break;

But for some reason I do not receive the second early state, but instead a confirmed. Although the notify_early_inuse_ringing is set to true for the extensions that generates the hint.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.