camel-sip-kafka-connector sink configuration

Required URI of the SIP server to connect to (the username and password can be included such as: john:secretmyserver:9999).

Should connections be cached by the SipStack to reduce cost of connection creation. This is useful if the connection is used for long running conversations.

Setting for contentSubType can be set to any valid MimeSubType.

Setting for contentType can be set to any valid MimeType.

Setting for a String based event type.

Setting for a String based event Id. Mandatory setting unless a registry based FromHeader is specified.

Hostname of the message originator. Mandatory setting unless a registry based FromHeader is specified.

Port of the message originator. Mandatory setting unless a registry based FromHeader is specified.

Username of the message originator. Mandatory setting unless a registry based custom FromHeader is specified.

The amount of time a message received at an endpoint is considered valid.

Setting for specifying amount of time to wait for a Response and/or Acknowledgement can be received from another SIP stack.

Name of the SIP Stack instance associated with an SIP Endpoint.

Hostname of the message receiver. Mandatory setting unless a registry based ToHeader is specified.

Portname of the message receiver. Mandatory setting unless a registry based ToHeader is specified.

Username of the message receiver. Mandatory setting unless a registry based custom ToHeader is specified.

Setting for choice of transport protocol. Valid choices are tcp or udp. One of: [tcp] [udp].

Enum values:

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

To use a custom AddressFactory.

A custom Header object containing call details. Must implement the type javax.sip.header.CallIdHeader.

An optional custom Header object containing verbose contact details (email, phone number etc). Must implement the type javax.sip.header.ContactHeader.

A custom Header object containing message content details. Must implement the type javax.sip.header.ContentTypeHeader.

A custom Header object containing event details. Must implement the type javax.sip.header.EventHeader.

A custom Header object containing message expiration details. Must implement the type javax.sip.header.ExpiresHeader.

A custom Header object containing user/application specific details. Must implement the type javax.sip.header.ExtensionHeader.

A custom Header object containing message originator settings. Must implement the type javax.sip.header.FromHeader.

To use a custom HeaderFactory.

To use a custom ListeningPoint implementation.

A custom Header object containing details on maximum proxy forwards. This header places a limit on the viaHeaders possible. Must implement the type javax.sip.header.MaxForwardsHeader.

Setting for maximum allowed Message size in bytes.

To use a custom MessageFactory.

To use a custom SipFactory to create the SipStack to be used.

To use a custom SipStack.

To use a custom SipURI. If none configured, then the SipUri fallback to use the options toUser toHost:toPort.

A custom Header object containing message receiver settings. Must implement the type javax.sip.header.ToHeader.

List of custom Header objects of the type javax.sip.header.ViaHeader. Each ViaHeader containing a proxy address for request forwarding. (Note this header is automatically updated by each proxy when the request arrives at its listener).

Name of client debug log file to use for logging.

Name of server log file to use for logging.

Logging level for tracing.

Number of maximum proxy forwards.

This setting is used when requests are sent to the Presence Agent via a proxy.

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.