[asterisk-bugs] [JIRA] (ASTERISK-26160) pjsip: Updated->Reachable during qualify

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-26160:
---------------------------------------

    Description: 
Depending on qualify frequency you may see Updated->Reachable messages quite often on the CLI these days. This can create a lot of noise and it also brings about the question: are these going over AMI?

This is caused by 7a14e669f073d6845ce4c13e8537b87fa4f3b042.

This brings about these questions:
1. Is this frequent state transition a good thing to have?
2. Is it useful?
3. Should we be outputting this transition so frequently?
4. Is this going out over AMI (which can create a LOT of messages)?
5. If going out over AMI should we stop it?

  was:
Depending on qualify frequency you may see Updated->Reachable messages quite often on the CLI these days. This can create a lot of noise and it also brings about the question: are these going over AMI?

This may have been caused by 9c2032240e4974fc4b6212f411c86c7d673006e3.

This brings about these questions:
1. Is this frequent state transition a good thing to have?
2. Is it useful?
3. Should we be outputting this transition so frequently?
4. Is this going out over AMI (which can create a LOT of messages)?
5. If going out over AMI should we stop it?


> pjsip: Updated->Reachable during qualify
> ----------------------------------------
>
>                 Key: ASTERISK-26160
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26160
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>            Reporter: Matt Jordan
>            Assignee: Richard Mudgett
>
> Depending on qualify frequency you may see Updated->Reachable messages quite often on the CLI these days. This can create a lot of noise and it also brings about the question: are these going over AMI?
> This is caused by 7a14e669f073d6845ce4c13e8537b87fa4f3b042.
> This brings about these questions:
> 1. Is this frequent state transition a good thing to have?
> 2. Is it useful?
> 3. Should we be outputting this transition so frequently?
> 4. Is this going out over AMI (which can create a LOT of messages)?
> 5. If going out over AMI should we stop it?



--
This message was sent by Atlassian JIRA
(v6.2#6252)