Acme Packet (MOSC)

MOSC Banner

Input on a HMR to change a 400 Bad Request to a 414 Request URI Too Long

edited Mar 9, 2013 7:16AM in Acme Packet (MOSC) 1 commentAnswered

The other thread where I got some input on craziness the LyncIT or Lync Interoperability Tool is sending for a test case.

 

Original thread

 

basically LyncIT is sending a call with an enormous Request URI and they say I should be responding with a 414 Request URI Too Long rather than the 400 Bad Request I am sending....

 

Example of the Request URI below and a HMR, wondring if there is a better way to do this HMR.

 

 

370705	30710.433506000	aaa.bbb.ccc.ddd	aaa.bbb.ccc.ddd	SIP/SDP	1374	Request: INVITE sip:+1NPANXXXXXX@themicrosoftlyncserverinteroperabilitytoolthemicrosoftlyncserverinteroperabilitytoolthemicrosoftlyncserverinteroperabilitytoolthemicrosoftlyncserverinteroperabilitytoolthemicrosoftlyncserverinteroperabilitytoolthemicrosoftlyncserverinteroperabilitytoolmicrosoft.com;ext=12345;user=phone | , with session description

The <wbr> does not exist in the URI, it is being added in from the code syntax highlighter.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center