search for: transport_name

Thanks, Michael. A few questions: Is [transport_name] a reserved word, or am I supposed to replace it with a name of my own, like '[did-transport]'? Some of the keywords I haven't seen before. Is ca_list_file supposed to be an aggregate of the public and private key? And what are the 'method,' 'tos' and 'cos'...

Hello Steve, use the following configuration for the transport and bind this transport to the trunk: [transport_name] type=transport protocol=tls bind=192.168.13.24 ; your bind IP ca_list_file=/etc/pki/tls/certs/ca-bundle.crt ; method=tlsv1_2 verify_server=yes allow_reload=no ;tos=0xb8 ;cos=3 external_media_address=your.ext.host.name ; hostname pointing to your ext. IP external_signaling_address=your.ext.host.na...

I want to configure communication with my phone provider using TLS for all the obvious reasons. Since I'm behind a firewall, I'll be needing to do it with NAT. There are examples of UDP plus NAT in pjsip.conf, but none for TLS plus NAT. Would it be correct to set up the TLS transport stanza to look like the [transport-udp-nat] stanza example, replacing UDP with TLS in lines like

Hi all, After finding multiples answers to this question via google, but without making it work on my servers. Has anybody iSCSI Offload working on a Dell Server with Broadcom NICs ? My environment: I'm running CentOS 5.6 CR, on a Dell PowerEdge R710 with Broadcom Corporation NetXtreme II BCM5709 conecting to an EMC CX4-120 SAN, via 2x Cisco 2960G-24TC-L switches. It's working