duggyk

I'm using openSUSE 10.3 any suggestions welcome !

If there's no way to remove the crypto line from the SDP when using UDP or TCP connections i'll have to find an alternative solution (end of trial) In my case the UA isn't offering any capabilities in the initial INVITE (no SDP). PBXNSIP is offering SDP in the 200OK (with crypto line even though the transport layer is UDP/TCP).

Is sending cryptographic information over a non-secure transport a good idea? I see that the a=crypto lines are sent whatever the transport layer (TCP/UDP/TLS)

I'm making calls whereby an INVITE without SDP is sent to PBXNSIP to initiate a call. PBXNSIP always seems to respond with a 200OK containing and SDP which contains a 'crypto' line (initiating SRTP when the calling device sends an ACK which contains the SDP). How can I stop PBXNSIP sending any crypto lines in SDP's (i.e. turn off SRTP) ???

I'm attempting to setup an auto attendant to work alongside a peer proxy ring-group application..... with no success yet...... Call flow goes a little like this.......... itsp >>> proxy >>> pbxnsip autoattendant caller dials an extenstion, call is routed back to proxy..... proxy <<< pbxnsip registered device (to proxy) rings ....... feature on proxy routes call back to pbxnsip if the call isn't answered...... proxy >>> pbxnsip call dies get strange error messages: [5] 2009/04/14 12:13:15: Received loopback request without tag [5] 2009/04/14 12:13:15: Received incoming call without trunk information and user has not been found what header declares the 'trunk information'? why is the user found when the same request URI is used (and the user is called directly)? make any sense?