Hi Amit,
Thanks so much for your prompt reply. Unfortunately I did not have
much success so far establishing a call between any two users
connected through the Mobicents server. Nevertheless I noticed that if
the user is online he is indeed detected, but then some sort of "loop"
problem occurs, and consequently I get a lot of exceptions. The end
result is that the call is not established. I am going to try to walk
you through one of the specific examples that originated this
behavior, and hopefully you can help me find the error. I conjecture
that the problem might be related with the default listening ports of
the SIP phones, but I am not at all sure.
Phones settings:
SIP Phone 1 (SPh1):
Twinkle 1.3.2.
user: hlouro
Domain: 127.0.0.1
Registrar: 127.0.0.1
Outbound Proxy:
127.0.0.1:5060
SIP port: 5070
RTP port: 8070
SIP Phone 2 (SPh2):
X-Lite 2.0 release 1105d build stamp 99999
user: torosvi
Auto Detect IP: No
Listen on IP: 192.168.43.128 but I also tried with 127.0.0.1 and I
obtained the same results ...
Listen SIP port: 5050
Listen RTP port: 8050
Outbound SIP Proxy: 127.0.0.1
Domain/Realm: 127.0.0.1
SIP Proxy: 127.0.0.1
Outbound Proxy:
127.0.0.1:5060
Use Outbound Proxy: Always
Send internal IP: Always
Register: Always
It would be an amazing help if you could take a look at the short
logFile (
http://www-personal.umich.edu/~hlouro/mobicents/) with the
details of all the test steps bellow.
Test steps:
0 - I am running Ubuntu on VMware in a PC running Windows XP.
1 - Connect to the JAIN-SLEE server by typing ./run.sh at the ..../
JBoss-xxx/bin folder level.
2 - Start Twinkle ( I get the message: " hlouro, registration
succeeded (expires = 3600 seconds)" )
3 - Start X-Lite
4 - To try to make hlouro (SPh1) establish a call with torosvi(SPh2).
I am trying to make the call by simply dialing sip:torosvi (or
sip:tor...@127.0.0.1) in SPh1. Should I dial 'torosvi' in any other
way? Should I specify the port? This way seems to follow the example
instructions, and it's the only one that lead to the (good - I guess)
log message:
" 04:51:48,484 INFO [SubscriptionProfileSbb] ########## User
sip:tor...@127.0.0.1 is available with contact
sip:tor...@192.168.43.128:5050 "
5 - The loop problem occurs right after and the call is not
established. Please take a look at the logFile that I have put in the
link above for details.
Answering your question of the previous post, the registration is
successful. I am sure of that when I run the example with Twinkle and
Ekiga (because both SIP phones give information about the number of
users registered). Furthermore, if while the server is running I add
and/or change one user in either Twinkle or Ekiga, the updated
information is immediately displayed on the phone. For example, if I
register 2/3/... users on a given phone, that phone will inform that
it it has 2/3/... users registered. Despite X-Lite does not "clearly"
give the information if the user is registered, it seems that it is
registering its users as well. At least when I change the user, that
change is reflected in the server's log.
I have tried to do a similar test with Ekiga and Twinkle, and with
Ekiga and X-Lite, and I ran into the same "loop" problems. Basically I
have tried everything that I could remember off to try to solve this
(including changing the Ekiga's default ports in the property file),
but I keep on running into this problem. I understood why the call
block and call forward work; it is because the CallBlockingSBB has
higher priority. I also confirm what you said regarding not listening
the voice mail when calling 'victor' from Twinkle, but listening it
when calling from another SIP phone.
It could also be really helpful if you could give me some details on
how you put the call-controller2 demo to work on your machine. Namely
which SIP phones you used, it's versions, it's settings, and how you
dialed the users (e.g.
sip:tor...@127.0.0.1 or
sip:tor...@127.0.0.1:5050; i.e. to use port or non-port).
I have successfully tested the 'conv-demo' and everything worked
nicely. That seems a strong evidence that there is nothing wrong with
the way I installed the JAIN-SLEE server, RA's, nor with the SIP
phones themselves. It might indicate a problem with the proxy's...
but I am kinda out of ideas for now.
Thanks you very much for your help,
Best
Hugo