Hi DanB,
I'm using the same functionality but never experienced this behavior.
Which version of SEMS are you using? Did you alter any of the click2dial
code?
What proxy software are you using for this? Could it be that it's
allowing only 1 simultaneous connection per account? And that as soon as
it's receiving an (authenticated) INVITE for the second call it's
closing the connection of the first call?
Regards,
Tom
-------- Originele bericht --------
Onderwerp: [Sems] click2dial auth issues
Van: Dan-Cristian Bogos <[email protected]>
Aan: [email protected]
Datum: 29-1-2009 14:43
Folks (not sure whether this email went to the right place first time,
so I am resending it),
I hit a strange problem by using click2dial via xmlrpc2di with auth.
Scenario: SEMS should dial the two destinations and bridge them
together, using auth for both calls.
Step-by-step actions:
1. SEMS dialing the first destination. All ok with auth, connection
established, playing the prompt.
2. SEMS dialing the second destination, auth challenged.
3. SEMS sending the second call with proper auth credentials, but
imediatelly after, disconnecting the first leg with sending BYE.
I should mention that the full scenario works just fine without using
Auth, therefore the conclusion with something wrong on auth side.
Attached the complete log for a call.
Thanks in advance for any tips.
Cheers,
DanB
------------------------------------------------------------------------
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
