Author
Topic: custom H323 header (Read 2862 times)

Is there any way to pass a custom SIP header as a h323 user-user header.

I have incoming SIP calls, containing a custome SIP header, which i need to pass inside an h323 call, so they can be intercepted by an Avaya AES, for onward integration. Any mechanism of getting the custom data over is valid, as i dont need the call records in yate or avaya to match ID/DID etc.

Currently using regexroute to target the avaya:

^5550005=h323/655201@10.11.10.20

have attenpted to pass SIP custom fields/h323 'userdata' header without any success.

Sending a custom SIP header is done via 'osip_' prefix. E.g. if you want to send a field called 'userdata', then in sip it would be osip_userdata=theactualdata.I am not sure for h323, but you can look into the yate source of the h323 module (maybe this: https://github.com/vir/yate/blob/master/modules/h323chan.cpp) or give oh323_userdata=<...> a try.