Dear Community,
Does somebody know if the parameter:
direct_media_method = update
Is shown as update in
pjsip show endpoint X
or is it always shown as: invite
Currently, i have method parameter with update value, but when i show the endpoint settings i see invite instead of update.
Im using asterisk-20.7-cert4 and im not sure how to propagate SDP changes through UPDATE method instead of re-INVITES.
Any ideas will be greatly appreciated
Warm Regards
You should ask your commercial support contact, as certified versions are only intended for users with such contracts.
Does the endpoint include UPDATE in its Allow header?
If it does, is UPDATE actually sent?
Hi David, thanks for the insights
I saw UPDATE in their supported headers but i didnt saw any UPDATE method sent,
and only the Media IP Address gets modified due direct media configuration between call leg B&C.
A > B (Me) > C
Do you know if the method parameter should always show update or invite regardless of the endpoint configuration? (Relaying in the .conf file)
Warm Regards
I asked about Allow, not Supports.
What does “Relaying in the .conf file” mean?
I’d need to check the code, but I was assuming that it would show update unless the remote side forbids it, but I note that the connected line method option update forces the use of update when not allowed.
Is there some reason why you want to use update?
(I was asking if update was actually used in case there was a problem with the CLI command.)
Hi there @david551 ,
i doublechecked the SIP headers replied from the remote trunk, and i have the following:
Allow: INVITE, ACK, BYE, CANCEL, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS, UPDATE
By:
What does “Relaying in the .conf file” mean?
I mean that im not sure if Asterisk shows the value of direct_media_method based on the configuration file or its value gets retrieved from SIP INVITES received from the remote endpoint.
I need to send update since re-invite are not supported by a call leg that is out of my reach
n… > A > B (me) > C
n… = Non visible call legs
The thing is that
I receive SIP 500 when i try to update the media addresses with a re-invite after codec negotiation was sucessful between A and B (Me), i know that A is not sending SIP 500, rather, A leg propagates SIP 500 from its own A leg (n… leg for me)
So I was looking to send UPDATE to see if that fixes the inconvenient, of course, if you have another suggestion, instead of using UPDATE or asking A leg’s to fix the inconvenient, please let me know
Warm Regards
UPDATE will be no different.
Dear @david551
What makes you think that SIP UPDATE is not supported?
Mind to elaborate a bit?
Warm Regards
UPDATE and INVITE reach the same distance, i.e. to the nearest UAS.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.