SIP

 

Why am I getting a Receive failure, due to insufficient buffer message?

If you get a receive failure, due to insufficient buffer, message on TransportUdpEventCallback the proxy has a buffer size configured that is inferior to the size of the message being sent.
Click here, for more information.

 

How can I set the audio recording path?

To change the audio recording path you must go to OneAdmin and edit the Storage configuration. Keep in mind you'll need full control over the folder you'll assign.
To know more about audio recording path configuration, click here.

 

What do the numbers mean on the logs concerning Radvision?

This are the Radvision error codes and their meaning:

Error Code Meaning
-1 There was an error, but we don't know specifics
-2  No resource left for this operation
-3  Parameter value invalid
-4 Required pointer parameter was a NULL pointer
-5  Parameter out of range 
-6  Operation attempted on a destructed object 
-7  Request not supported under current configuration 
-8  Object uninitialized 
-9  Incomplete operation, used by semaphore's try lock 
-10 The requested action is illegal
-11 Action failed due to network problems
-12 A handle passed to a function is illegal
-13 The requested item cannot be found
-14 The buffer is too small
-15 RV_ERROR_TIMEOUT -15
-16 To signal UDP receive failure, usually due to ICMP message
-17 The bind on the socket failed due address unavailability
Default Unknown Error

 

In case of Radvision exception, on CallControl, the log is printed in the following format:
"RadVisionException in function {function } with error {error code}: {message} {stack trace}"

My agent can hear the client, but the client can't hear the agent and the agent's sound isn't on the recorded interaction.  What can we do to solve this?

If there's sound on the client side, first make sure that OneMedia is receiving RTP on both legs:

  • Check the logs and search for REC B: (each B is a different leg for the same call).
  • Check WI: on both legs.
  • If they're rising RTP is being received.
  • If RTP is being received but on the agent's side is silence:
    • Check if the agent has the proper mic selected.
    • Check if the mic wasn't added or removed without a logout/login.

 

OneSIPConnector stopped receiving SIP messages. What can i do?

If OneSIPConnector stopped receiving SIP messages, please perform the following checks:

  1. Check if there's a bug related with this issue.
  2. Check if no firewall is configured for this port.
  3. Assure that in wireshark you can see the messages reaching OneSIPConnector in correct port and IP.

 

OneProxy doesn't start. What can I do?

When there's an error with OneProxy's , check the logs and look for LocalAddressOpen:

17349.png

The failed to open local UDP address can be caused by:

  • The IP 180.240.134.237 exists on the server machine. Check with the command ipconfig /all to confirm.

  • The port might be already in use. Check if the selected port is already in use, with the command: netstat -nao | find "5060"

 

Sometimes the gateway sends DTMF without end. What can we do about it?

If the gateway sends DTMF without end, you can configure OnePark to read DTMFs without end. Use the advanced parameter UseDTMFEnd on OneAdmin. To know hoe t oconfigrue advanced parameters, click here.

 

Application crash. What do we need to analyze the issue?

To analyze an application crash we need to the following information:

  • Event viewer with crash event
  • Application crash dump file (how to)
  • Application logs (real time, if possible)
  • OS version
  • .NET version
  • OneContact version & application dll's (because there might be different hotfixes applied)