SPA3102 invite problem

[gianfranco_liberars]

For USER english:

Scenario:

1 spa 3102 - 1001 User

A SIP server

1 spa 921 - 101 user

1 spa 922 - 102 user

This is what happens:

101 user call external line to 0622222 ....

sip server route call on SPA3102

spa 3102 call 0622222 .... and connects with 101

While the two talk 102 tries to make a call and bind the PSTN line 1001

spa 3102 responds with the message 503 (correctly because the line is busy state)

102 close call

After a few seconds when 101 and 0622222 .... are still connected, spa 3102 sends an invitation to sip server containing the two people in line.

Send an invitation as if it were a new incoming call, but it is the same as before.

Is there any setting to configure to prevent them, what does not happen?

[Eric Moyers · Accepted solution]

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.

I would like to make sure that I understand your issue correctly:

1. When the SPA921(101) user calls out PSTN line to 0622222, your SIP server connects to the 3102 and connect the call out the PSTN.
2. While the SPA921 (101) is still talking, SPA922(102) tries to make a call out the PSTN line also.
3. THe SPA3102 responds with the message 503 (correctly because the line is busy state) and the SPA922(102) closes the call.
4. After a few seconds, while SPA921(101) and 0622222 .... are still connected, spa 3102 sends an invitation to sip server containing the two people in line as if it were a new incoming call, but it is the same as before and still gets a busy signal.

If I am correct, then it I feel that this may be to much to try and troubleshoot through email on this forum. My best suggestion would be give our support center a call and let one of our VOIP agents help resolve this issue.

You can contact the SMall Business Support Cent at 1-866-606-1866 or contact our Sophia, Bulgaria support center at +442077603350

Eric Moyers
Cisco Network Support Engineer
1-866-606-1866

[gianfranco_liberars]

Hi Eric Moyers,

this is a bug of version 5.0, in last version this issue is solved.

Regards

Gianfranco