Hi,
Here is the original reporter of the issue at Asterisk's issue tracker.
So you say you provider's Asterisk doesn't send Max-Forwards? That would
be strange as it's a behavior that breaks the protocol and a lot of
softphones would fail to operate with your provider, which I don't think
is the case (this issue was discovered soon after Asterisk switched to
PJSIP stack, so the implementation was not well tested yet). Asterisk
already fixed it and for the old versions there's a configuration option
(type=global).
If it's really the case (i.e. your provider is running an outdated
version of Asterisk which is NOT RFC3261 compliant and they didn't apply
the config work-around), then I believe your provider should take the
necessary steps to solve the issue or you switch to another provider.
RFC3261 at page 35 <https://tools.ietf.org/html/rfc3261#page-35> says:
"A valid SIP request formulated by a UAC *MUST*, at a minimum, *contain*
the following header fields: To, From, Cseq, Call-ID, *Max-Forwards*,
and Via; all of these header fields are *mandatory* in all SIP requests")
Regards,
Anatoli
*From:* John Statler
*Sent:* Wednesday, January 25, 2017 18:21
*To:* Linphone-users
*Subject:* Re: [Linphone-users] Hang up at about 30 seconds - incoming
calls, with log
Sorry for the duplicate post, didn't realize Subject was wrong.
Reposting just to keep some kind of sense to it all.
I found an interesting report on the Asterisk issues site
(https://issues.asterisk.org/jira/browse/ASTERISK-24807) directly
related to ' Missing mandatory header [Max-Forwards],'
I sent my log and the Asterisk link to my VoIP service provider in the
(maybe remote) chance they will understand the fix Asterisk used.
The following, though I understand little of it, is from that Asterisk
issue site.
The intent is for Max-Forwards to be added by default to outbound
SIP requests. In res_pjsip/config_global.c, the Max-Forwards and
User-Agent headers are configured to be added to outbound
requests. Then the PJSIP module in
res_pjsip/pjsip_global_headers.c is intended to send those headers
out on each request.
My guess here is that this is another instance of that
all-too-common config framework/sorcery mistake where the absence
of a configuration section results in expected default values not
being applied. As an experiment, in your pjsip.conf file, can you
add the following:
[global]
type = global
Adding a global configuration section should result in the default
Max-Forwards and User-agent headers being applied. If this fixes
the problem, it should be easy to create a patch to fix this.
If my provider can't fix it, do you think there is any way for me to
remove the requirement for that header?
Do you think the header exists on a Linphone to Linphone connection
but not on the cell phone to Linphone connection?
Thanks for taking the time to review this issue.
John.
On 1/25/2017 7:51 AM, [email protected] wrote:
In this case linphone doesn't like the ack it's received.
message: 2017-01-25 04:54:33:115 channel [034002A0] [348] bytes parsed
error: 2017-01-25 04:54:33:115 Missing mandatory header
[Max-Forwards] for message [ACK]
In the interest of brevity I did not include my log in this message.
--
John Statler
*Computer Services Northwest*
541-770-5524
_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users
_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users