03-02-2010 02:25 PM - edited 03-21-2019 09:24 AM
I've got an easily reproducable problem with call waiting on a WRP400. Here's the scenario:
A (voip user) calls B (WRP400). B answers and establishes a call.
C (voip user) calls B. Call waiting notifies B of the call. B hangs up with A and takes the call with C.
Within 30 seconds, the call between B and C will terminate. Debug logs on the WRP400 indicate the call is cleaned up, but no BYE is sent.
When C gives up and sends a BYE, the WRP400 will respond 481 Transcation Does Not Exist.
This is using the 1.01.00 firmware. I defaulted the WRP400 and entered just a proxy, username and password and still had the problem.
Now here's the weird part. I rolled back to the 1.00.06 firmware and the problem has gone away. That seems to indicate it's a bug in the 1.01.00 firmware.
Ever heard of such a thing?
03-03-2010 04:51 AM
Dear Sir;
Do you have network traces that show the behavior? If so please attach it.
Regards
Alberto
03-08-2010 03:50 PM
Here are the syslog messages I received from the ATA during a call.
First I placed a call to the ATA (10.42.42.85).
Feb 26 16:48:07 10.42.42.85 [0:0]AUD ALLOC CALL (port=16412)
Feb 26 16:48:07 10.42.42.85 [0:0]RTP Rx Up
Feb 26 16:48:07 10.42.42.85 pconly: 0
Feb 26 16:48:07 10.42.42.85 n: 2
Feb 26 16:48:07 10.42.42.85 clRemote: 0xbd9ffaa0, clLocal->ucNumAudioCodec: 2
Feb 26 16:48:09 10.42.42.85 CC:Connected
Feb 26 16:48:09 10.42.42.85 [0:0]ENC INIT 0
Feb 26 16:48:09 10.42.42.85 [0:0]RTP Tx Up (pt=0->bd2a2a0a:8000)
Feb 26 16:48:09 10.42.42.85 [0:0]RTCP Tx Up
Feb 26 16:48:09 10.42.42.85 [0:0]DEC INIT 0
Feb 26 16:48:09 10.42.42.85 [0:0]RTP Rx 1st PKT @16412(2)
Feb 26 16:48:12 10.42.42.85 [0:0]LAT++ 7(2)
Feb 26 16:48:14 10.42.42.85 [0:0]LAT++ 8(2)
Feb 26 16:48:15 10.42.42.85 [0:0]RTP Tx Dn
At this point the first call is up. I then placed the second call.
Feb 26 16:48:17 10.42.42.85 [0:1]AUD ALLOC CALL (port=16414)
Feb 26 16:48:17 10.42.42.85 [0:1]RTP Rx Up
Feb 26 16:48:17 10.42.42.85 pconly: 0
Feb 26 16:48:17 10.42.42.85 n: 2
Feb 26 16:48:17 10.42.42.85 clRemote: 0xbd9ffaa0, clLocal->ucNumAudioCodec: 2
I hung up the first call.
Feb 26 16:48:20 10.42.42.85 [0:0]AUD Rel Call
Feb 26 16:48:20 10.42.42.85 [0]On Hook
I answered the second call.
Feb 26 16:48:21 10.42.42.85 CC:Connected
Feb 26 16:48:21 10.42.42.85 [0:1]ENC INIT 0
Feb 26 16:48:21 10.42.42.85 [0:1]RTP Tx Up (pt=0->bd2a2a0a:8002)
Feb 26 16:48:21 10.42.42.85 [0:1]RTCP Tx Up
Feb 26 16:48:21 10.42.42.85 [0:1]DEC INIT 0
Feb 26 16:48:21 10.42.42.85 [0]Off Hook
The second call went just fine for a while.
Feb 26 16:48:21 10.42.42.85 [0:1]RTP Rx 1st PKT @16414(2)
Feb 26 16:48:24 10.42.42.85 [0:1]LAT++ 7(2)
Feb 26 16:48:27 10.42.42.85 DLG Terminated 19c340
Feb 26 16:48:27 10.42.42.85 Sess Terminated
This is when the audio from the ATA stopped. I never received a BYE notice for the second call.
Feb 26 16:48:40 10.42.42.85 CC:Clean Up
Feb 26 16:48:40 10.42.42.85 DLG Terminated 19c3d4
Feb 26 16:48:40 10.42.42.85 Sess Terminated
Feb 26 16:48:40 10.42.42.85 [0:1]AUD Rel Call
Feb 26 16:48:43 10.42.42.85 [0]On Hook
I tried a number of variations on this same theme (flash to second call, caller hang up, etc.) and it's pretty consistent.
03-09-2010 06:29 AM
Dear Sir;
Any network traces that shows SIP messages?
Regards
Alberto
03-09-2010 07:40 AM
I thought I had full debugging turned on, but I did not. I will generate some new calls and update soon.
03-10-2010 10:31 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide