Hello All,
We are trying to connect an external application to the 3CX PBX using SIP TRUNK.
When the app makes a call to the 3CX PBX, it sends (of course) an INVITE command to the PBX. The 3CX PBX responds with a PROXY AUTHENTICATION request. That's OK, of course, and the app responds with the proper PROXY AUTHENTICATION and everything is OK.
However, if the app tries to put the call on HOLD, it sends the PROXY AUTHENTICATION as part of the header - that's the way it should be, according to the SIP RFC. However, the 3CX PBX doesn't want the PROXY AUTHENTICATION on the HOLD request...
Is there a way to configure this differently?
Thanks.
We are trying to connect an external application to the 3CX PBX using SIP TRUNK.
When the app makes a call to the 3CX PBX, it sends (of course) an INVITE command to the PBX. The 3CX PBX responds with a PROXY AUTHENTICATION request. That's OK, of course, and the app responds with the proper PROXY AUTHENTICATION and everything is OK.
However, if the app tries to put the call on HOLD, it sends the PROXY AUTHENTICATION as part of the header - that's the way it should be, according to the SIP RFC. However, the 3CX PBX doesn't want the PROXY AUTHENTICATION on the HOLD request...
Is there a way to configure this differently?
Thanks.
