I have followed Orig append format and it does not work, Is there any use case or correct format to use this field?
As per documentation, below is what it says and it doesn’t seem to work, has anyone tried to test it or is it still not fully developed? looking for some feedback
Orig append headers req
Additional SIP headers that Yeti should add to request to the Gateway (in case of using Gateway as Originator of calls). Additional header fields are lines composed of a field name, followed by a colon (:), followed by a field body, and terminated by followin set of characters (‘rn’). A field name must be composed of printable US-ASCII characters (i.e., characters that have values between 33 and 126, inclusive), except colon. A field body may be composed of any US-ASCII characters, except for carriage return character (‘r’) and line feed character (‘n’). Format of headers: field-name1: field-value1**rn**field-name1: field-value2…, where *field-name1 and field-name2* - names of the custom fields, *field-value1 and field-value2* - values of the custom fields, **rn** - the carriage-return/line-feed pair.
It is actually a very useful use case when you have scenarios like the one below:
5 Origination Gateways and 1 Termination Gateway
3 our 5 origination gateways are required to send additional sip headers in leg A so the termination gateway can have specific header like P-asserted-identity and privacy header, etc carried forward from Leg A. otherwise the termination gateway will drop the call.
Currently, we have to duplicate termination gateways for every origination gateway
1 origination gateway = 1 same termination gateway and use term append header req in leg B, which is a system overkill
As discussed internally, we will look forward to you adding this feature in the future.