Hi Stephanie,
On 03/31/2010 05:32 PM, Stephanie Vigil wrote:
When we run SEMS its working with the conference, but when we run ser
and sems together, ser kills sems, then the conference does not work.
I'm not sure what you mean by "kills." It seems to me, however, that
the most likely explanation is that you are having SEMS and SER bind to
the same UDP port (5060) on the same host.
Sems is registered at 4444 with user name Alice. Can you please look at
our codes (SER and SEMS) and tell us what we are doing wrong. It seems
like SER does not recognize Alice. I dont understand how I can see that
SER and SEMS are connecting, can you please explain how it should look
like? We are running Wireshark to view our responses (ACK, OK, BYE
messages) and we keep getting 404 on line sl_send_reply ("404", "NO
CONFERENCE"); this is in SER and we are also getting 483 Too Many Hops.
This too sounds symptomatic of having both services run on the same host
bound to the same port; 483 Too Many Hops means SER's main request
block is finding a routing loop.
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
