Avaya Aura MS rejects incoming SIP sessions

Last Updated : Dec 16, 2016 |

Avaya Aura® MS rejects SIP sessions in the following manner:

  • Avaya Aura® MS rejects incoming SIP sessions for one or more service types. Use the Log Viewer to identify attempts to launch an uninstalled or unlicensed service.

  • Avaya Aura® MS rejects incoming SIP sessions. You see SIP failure responses such as 305 Use Proxy, or 403 Forbidden, in the message traces or logs.

Possible causes for these problems include:

  • Calls to services on Avaya Aura® MS that are not licensed, receive a SIP final response indicating that the service is unavailable.

  • The proxy configuration is incomplete.

  • The target service application is not installed.

  • Avaya Aura® MS is in the Pending Lock state.