SIP INFO with "stop callwaitingtone" to Adtran 9xx results in "501 Not Implemented" response.

[mhess]

I have a BroadWorks environment configured to send SIP Info messages to my Adtran 924 to indicate call waiting.  The Adtran receives the initial Info with SDP "play tone CallWaitingTone1" and responds with 200 OK, but when BroadWorks sends the "stop CallWaitingTone" Info message the Adtran responds with "501 Not Implemented".

SDP details:

Content-Length:   22

Content-Type: application/broadsoft

   stop CallWaitingTone

Is the a configuration issue?

[jayh]

Probably not.  What does the receiving party hear?  If a call waiting tone that plays once and stops, it's OK.

If anything it may be a configuration option in Broadworks.

If the end device is an IP phone with a display, then the waiting call will stay on the display until the waiting caller hangs up or is transferred to voice mail, then the "stop" message will cause the display to show the call no longer waiting.

If the end device is an FXS port or similar, the "play" message causes a one-time event to send a beep to the handset.  Telling it to stop does nothing (it's a short beep) so the Adtran indeed doesn't implement that. 

[Anonymous · Accepted solution]

Mr. Hess,

Thanks for posting.  Adtran's current recommendation is to send in the second call with a new Invite instead of using the SIP INFO message. 

Thanks!

David

[mhess]

Thanks for clarification Jay.  Receiving party is FXS and doesn't hear anything in response to the "stop callwaitingtone".  Problem appears to be benign but wanted to see if there was a way to stop it and cut down on unnecessary messages.

[mhess]

Thanks David.  We're investigating this alternative as it will solve some additional issues as well.