Opened 5 years ago
Last modified 2 years ago
#9 new defect
Credentials missing in ACK
| Reported by: | chris-mac | Owned by: | vadim |
|---|---|---|---|
| Priority: | trivial | Milestone: | |
| Component: | phapi | Version: | 2.3 |
| Keywords: | Cc: |
Description
Just found out that QuteCom is not sending ACK in response to 200/OK with credentials as required by RFC 3261 - section 13.2.2.4:
[...]
The sequence number of the CSeq header field MUST be the same as the INVITE being acknowledged, but the CSeq method MUST be ACK. The ACK MUST contain the same credentials as the INVITE. [...]
Change History (5)
comment:1 Changed 5 years ago by vadim
comment:2 Changed 5 years ago by chris-mac
- Priority changed from major to trivial
At some point I had impression Asterisk doesn't like ACKs form QuteCom and is retransmitting 200/OK over and over again. However it turned out later this problem was not related to QuteCom at all.
So it is definitely not a show stopper (I am changing priority to trival).
On the other hand would be nice to make QuteCom RFC 3261 complaint when the time allows.
comment:3 Changed 4 years ago by vadim
- Milestone changed from QuteCom 2.2-RC2 to QuteCom 2.3
comment:4 Changed 3 years ago by chris-mac
- Version changed from 2.2-RC1 to 2.3
comment:5 Changed 2 years ago by dneary
- field_os set to all
- Milestone QuteCom 2.3 deleted
Moving off 2.3 milestone, since this seems like a minor issue.
Dave.
Is this a show stopper?
I didn't see a sip server yet which considered this to be a problem