[asterisk-bugs] [JIRA] (ASTERISK-29667) Asterisk sends with the wrong Nonce to the Telecom operator for the Registration Packet.

[Vijo Jose (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=256505#comment-256505 ] 

Vijo Jose commented on ASTERISK-29667:
--------------------------------------

As checked the Wireshark traces shared filename Trace_27092021_1157.pcap
  
For some rare cases where asterisk sending the new Register request wth updated nonce but most of the cases the asterisk is not sending registration request with updated nonuse - it just keeps sending with an old nonce.

Refering the call-id - 3b02fa216d1e3f777ceba1d714480b35

What could be the reason for this ? or how should we take it forward ?

The SIP account multiple DID - Around 30 DID's am registering in the sip.conf

> Asterisk sends with the wrong Nonce to the Telecom operator for the Registration Packet.
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29667
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29667
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Channels/chan_sip/Registration
>    Affects Versions: 16.17.0
>         Environment: OS : CentOS Linux release 7.9.2009 (Core)
> Asterisk : Asterisk 16.17.0
> Chan_sip used 
>            Reporter: Vijo Jose
>            Assignee: Vijo Jose
>         Attachments: 27-09-2021.zip, Asterisk_ChanSIP_Nounce_22092021.txt, logging.txt
>
>
> I have a SIP trunk from a telecom operator which is registered on the Asterisk Box.
> Asterisk sends with the wrong Nonce to the Telecom operator for the Registration Packet and due to this the operator rejects the sip registration packet.
> Asterisk was supposed to send the registration request with Nonce received from the previous unauthorized from Telecom operator and with new Cseq number. But the same is not happening intermittently.



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