Hi Dhiraj!
I have a similar problem as you described, actually "solved" it by an ugly
hack (hard coding) in the Python code. You said, that you have solved it
by setting the db_url bit for the domain module.
Could you please explain me what exactally you did to make it work? What
did you change in ser.cfg?
Thanks in advance.
cheers,
Bernie
On Wed, 16 Jun 2004 dhiraj.2.bhuyan(a)bt.com wrote:
Thanks Adrian.
Its working now :)
I missed the db_url bit for the domain module in ser.cfg
Regards,
Dhiraj
-----Original Message-----
From: Adrian Georgescu [mailto:ag@ag-projects.com]
Sent: 16 June 2004 13:42
To: Bhuyan,D,Dhiraj,XSG1 R
Cc: serusers(a)lists.iptel.org
Subject: [Serusers] Mediaproxy | none of caller or called party is local
Dhiraj,
Mediaproxy is looking in From: and To: Make sure the domains of either user is in ser
domain table
Example: For user 1234(a)bt.com
serctl domain add
bt.com
Adrian
--------
Hello List,
I am trying to set up the following senario -
[kphone A]-----------[ser/mediaproxy A]---------------------[ser/mediaproxy
B]-----------[kphone B]
When I try to set up a call between the two ends, proxydispatcher complains that
"none of the caller or called party is local. will not use mediaproxy".
I am not using DNS SRV at the moment - instead will be using the default unix socket.
Kphone A and B are registered respectively to ser/mediaproxy A and B respectively.
Anybody has any hint where this thing might be failing? I tried to go through the code -
but python is not one stronghold. How does the dispatcher decide whether "caller or
called" party is local?
Thanks for your help,
Dhiraj Bhuyan
Network Security Specialist,
BT Exact Business Assurance Solutions
Tel: +44 1473 643932
Mob: +44 7962 012145
Email: dhiraj.2.bhuyan at
bt.com