-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have problems with a remote server, outside of my control, that seems
to have very broken request URI handling. It is possibly suffering from
an Asterisk bug [1] or something similar.
On my side I have a UAC (IP address 172.16.1.102) and a SER 2.0 proxy.
The UAC sends an INVITE, and the remote UAS ends the dialog with a BYE
request. However this BYE returns to my proxy with missing route
headers, so SER cannot route it. I need to work around the problem with
SER on my side and wonder what the best solution is.
Here is the relevant part of the conversation as seen on my proxy
80.81.82.3 (slightly massaged, irrelevant parts cut):
INVITE sip:00463112341234@proxy.remote.com SIP/2.0.
Record-Route: <sip:80.81.82.3;avp=Z3oDBwBhY2NvdW50AwB5ZXM;lr>.
Call-ID: f730a3a6a5c450508274739a8133ae7f(a)172.16.1.102.
CSeq: 1 INVITE.
To: <sip:00463112341234@proxy.remote.com>.
From: <sip:17473605948@proxy.remote.com>;tag=2045565953650740630.
Via: SIP/2.0/UDP 80.81.82.3;branch=z9hG4bK761b.b1548ac4.0.
Via: SIP/2.0/UDP
172.16.1.102:5060;rport=5060;appname=myapp;branch=z9hG4bK74592b710287e6cfa94b4cf9c10e15bf.
Contact: "17473605948" <sip:172.16.1.102:5060;transport=udp>.
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 80.81.82.3;branch=z9hG4bK761b.b1548ac4.0.
Via: SIP/2.0/UDP
172.16.1.102:5060;rport=5060;appname=myapp;branch=z9hG4bK74592b710287e6cfa94b4cf9c10e15bf.
Record-Route: <sip:123.12.13.14;lr;ftag=2045565953650740630>.
Record-Route: <sip:80.81.82.3;avp=Z3oDBwBhY2NvdW50AwB5ZXM;lr>.
From: <sip:17473605948@proxy.remote.com>;tag=2045565953650740630.
To: <sip:00463112341234@proxy.remote.com>;tag=as438ee174.
Call-ID: f730a3a6a5c450508274739a8133ae7f(a)172.16.1.102.
CSeq: 1 INVITE.
Contact: <sip:011463112341234@130.94.88.93:5060>.
ACK sip:01146739835569@130.94.88.90:5060 SIP/2.0.
Record-Route: <sip:80.81.82.3;avp=Z3oDBwBhY2NvdW50AwB5ZXM;lr>.
Call-ID: f730a3a6a5c450508274739a8133ae7f(a)172.16.1.102.
CSeq: 1 ACK.
Via: SIP/2.0/UDP 80.81.82.3;branch=0.
Via: SIP/2.0/UDP
172.16.1.102:5060;rport=5060;appname=myapp;branch=z9hG4bK96a96b64dfd5aba5c896c37e0de18850.
From: <sip:17473605944@proxy.remote.com>;tag=7737826714334905221.
To: <sip:0046739835569@proxy.remote.com>;tag=as543c9f3f.
Route: <sip:123.12.13.14;lr;ftag=7737826714334905221.
Content-Type: application/sdp.
BYE sip:80.81.82.3:5060 SIP/2.0.
Record-Route: <sip:123.12.13.14;lr;ftag=as438ee174>.
Via: SIP/2.0/UDP 123.12.13.14;branch=z9hG4bK100d.d617f387.0.
Via: SIP/2.0/UDP 130.94.88.93:5060;branch=z9hG4bK0256ad7c;rport=5060.
Route: <sip:80.81.82.3;avp=Z3oDBwBhY2NvdW50AwB5ZXM;lr>.
From: <sip:00463112341234@proxy.remote.com>;tag=as438ee174.
To: <sip:17473605948@proxy.remote.com>;tag=2045565953650740630.
Call-ID: f730a3a6a5c450508274739a8133ae7f(a)172.16.1.102.
CSeq: 102 BYE.
I think this BYE is incorrect. It should have the originator's Contact
(sip:172.16.1.102:5060;transport=udp) in the request URI and the
Record-Routes of the original INVITE in the Route header. Or, if it is a
strict router, it could have the current request URI but add the Contact
as the last Route header. Now it has destroyed the originator's route
information. What is the best way to get SER to remember/reconstruct
this last hop to the UAC?
Cheers,
Marcus
[1] http://bugs.digium.com/view.php?id=3609
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkjXkbQACgkQXjXn6TzcAQnhrQCeP9T0pR+AlPJjTr8OCS5nNOAA
GBIAnR5pw68rqe1PR00jDLvcYh+eQXPP
=sdca
-----END PGP SIGNATURE-----
Hi!
FYI: I just found this one:
http://carrierclass.net/
looks like it is a central management webinterface for a
openser-asterisk setup.
regards
klaus
Hi
I am trying to call a script via exec_avp and then use the output of the
script to use as an argument to forward(). Such as
route[2] {
# forward to AGCF
exec_avp("/usr/utils/select_incoming_agcf.php");
record_route();
xlog("forward to: $avp(i:1)\n");
#forward("$avp(s:1)");
forward("$avp(s:1);
exit;
}
However syslog complains as follows
Sep 18 11:42:12 vla openser[19470]: ERROR:core:parse_phostport: bad protocol
in $avp(s:1)
Sep 18 11:42:12 vla openser[19470]: ERROR:core:fix_actions:
ERROR:fix_actions: FORWARD/SEND bad argument
Sep 18 11:42:12 vla openser[19470]: ERROR:core:main: failed to fix
configuration with err code -6
The output of the script is 10.0.0.1:5060
Any ideas?
Regards
Jon
Hello all,
I'm running openser 1.2.2, and i want to make/receive pstn calls. I have
installed asterisk 1.4. in the same machine. Do I need to change the port in
asterisk? and how to do it?
What are the basic lines in the configuration files of asterisk to
accomplish that? I don't think I have problem with openser.cfg.
Sorry about the questions but I don't seem to find the exact documentation I
need.
Thanks in advance!
Tiago Res
Hi ALL,
I installed openxcap 1.0 version and its dependences.
When i run "openxcap --no-fork" and openser 1.3.2v.
I am getting these errors.
*************************************************************************************************************
[root@info infopresence-1.2.0-tls]# openxcap --no-fork
Starting Open XCAP 1.0.0
Traceback (most recent call last):
File "/usr/local/bin/openxcap", line 53, in <module>
from xcap.server import XCAPServer
File "/usr/local/lib/python2.5/site-packages/xcap/server.py", line 21, in <module>
from xcap import authentication
File "/usr/local/lib/python2.5/site-packages/xcap/authentication.py", line 21, in <module>
from xcap.appusage import getApplicationForURI, namespaces
File "/usr/local/lib/python2.5/site-packages/xcap/appusage/__init__.py", line 42, in <module>
class ServerConfig(ConfigSection):
File "/usr/local/lib/python2.5/site-packages/xcap/appusage/__init__.py", line 45, in ServerConfig
backend = Backend('Database')
File "/usr/local/lib/python2.5/site-packages/xcap/appusage/__init__.py", line 40, in __new__
raise ValueError("Couldn't find the '%s' backend module: %s" % (value.lower(), str(e)))
ValueError: Couldn't find the 'database' backend module: No module named _mysql_exceptions
[root@info infopresence-1.2.0-tls]#
********************************************************************************************************************
Here with i am enclosing the config.ini file.
Please guide me on this.
Thanks & Regards,
Mahesh Peddi