Hi DanB,
Ok, but I don't see how (and why) you would want to use both b2bua and
click2dial in the same setup. As far as I can see b2bua and click2dial
are doing similar things. But I must say that I have no experience in
using b2bua. I just skimmed the b2bua.org website...
Can you give us some more insight in what your setup looks like?
Regards,
Tom
-------- Originele bericht --------
Onderwerp: Re: [Sems] click2dial auth issues
Van: Dan-Cristian Bogos <[email protected]>
Aan: [email protected]
Datum: 30-1-2009 13:21
Again, sorry for flooding, hit some issues with my email client
(gmail.com vs. googlemail.com issues).
Back to the problem:
I did not modify in any way click2dial application. The software I am
sending the calls through is B2BUA (b2bua.org), which does not have any
limitation of simultaneous usage. From the trace it looks like SEMS is
the one dropping the first call (although could not find much
explanation in the logs). Could be that some header is not as expected
or something else, not sure where to start about that since there is no
error.
I thought that before going into sources to try asking if anyone got
similar issues, since my C++ skills are not yet at the right level ;).
Thanks,
DanB
Message: 4
Date: Fri, 30 Jan 2009 11:51:03 +0100
From: Tom van der Geer <[email protected]>
Subject: Re: [Sems] click2dial auth issues
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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
End of Sems Digest, Vol 63, Issue 17
************************************
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
