/usr/local/sbin/ser start
0(4138) ERROR: load_module: could not open module
</usr/local/lib/ser/modules/m
ysql.so>: /usr/local/lib/ser/modules/mysql.so: cannot open shared object
file: N
o such file or directory
0(4138) parse error (76,13-49): failed to load module
ERROR: bad config file (1 errors)
Shiran Guez
Hi,
I'm trying to have a caller (eg sender of invite) be able to detect the
difference between a user that is 'offline' and one that really doesn't
exist. Current cfg methods allow for doing a lookup in the location
table, but if the target isn't there - then a 404 is returned.
I think what I would like to do is then check the subscriber table....what
is the best way to accomplish this?
(trying a 'lookup' on the subscriber table didn't work....)
Thanks in advance.
Jim.
400 Table 'aliases' not found in memory, use save("aliases") or
lookup("aliases") in the configuration script first
I have set the aliases in the ser.cfg file and this message is not changing
can some one help please?
Shiran Guez
Hi,all
I try to use the module(msilo) to implement web Message Store.
I add this part in my ser.cfg
loadmodule "/usr/local/lib/ser/modules/msilo.so"
modparam("msilo", "registrar", "sip:registrar@<my_domain>")
modparam("msilo", "db_url", "mysql://ser:heslo@dbhost/ser")
and I can't start my ser server.
It appear this error.
Sep 15 17:36:35 knuth /usr/local/sbin/ser[7092]: MSILO:mod_init: Wrong
version v2 for table <silo>, need v3
Sep 15 17:36:35 knuth /usr/local/sbin/ser[7092]: init_mod(): Error while
initializing module msilo
my ser is download by cvs.
could anyone call solve it.
thanks.
Mahesh,
I don't see anything wrong with IPTEL's proxy server. It's behaving well.
The ACK is sending to HOST2 via the their proxy. What exactly is your
problem?
BTW, what kind of SIP-ALG are you using. It's kind of strange that it has a
different CONTACT header yet it works.
Zeus
> -----Original Message-----
> From: mahesh [mailto:mahesha@intoto.com]
> Sent: Wednesday, 15 September 2004 7:12 PM
> To: Zeus Ng
> Cc: serusers(a)lists.iptel.org
> Subject: RE: [Serusers] Proxy sending ACK on port 5060
> instead of on contact port
>
>
> Hi Zeus,
>
> I am attaching the ethereal captures of both fw1 and fw2(on
> wan interfaces). The NAT IP used by fw1 is 202.125.84.164 and
> the one used by fw2 is
> 202.125.84.163
>
> regards
> Mahesh
>
>
> >Mahesh,
> >
> >Given that you have ethereal capture, send it in to the list
> and we can
> >see what's happening.
> >
> >Zeus
> >
> > > -----Original Message-----
> > > From: serusers-bounces(a)lists.iptel.org
> [mailto:serusers-bounces@lists.iptel.org]
> > > On Behalf Of mahesh
> > > Sent: Wednesday, 15 September 2004 5:15 PM
> > > To: serusers(a)lists.iptel.org
> > > Subject: [Serusers] Proxy sending ACK on port 5060 instead of on
> > > contact port
> > >
> > >
> > > Hi all,
> > >
> > > I am using the following configuration to test SJPhone
> through IPTEL
> > > proxy server(publicly
> > > available:195.37.77.99).
> > >
> > > HOST1(win2K)---FW1---Internet---FW2---HOST2(winXP)
> > >
> > > Host1 and Host2 are hosts with private IPs having SJPhone
> > > application. FW1 and FW2 are
> > > firewall/NAT devices with SIP-ALG implementation. This means
> > > all the SIP
> > > messages are modified to include the public IPs in them. Also the
> > > via,contact ports are modified. Now both host1 and host2
> > > register with the iptel proxy server. A call is initiated
> > > from host1. Host2
> > > sends 200 OK response
> > > to the HOST1. After this the ACK sent by Host1 is sent to
> > > port 5060 on
> > > HOst2,instead of the
> > > contact port advertised in 200 OK. This is observed from
> > > ethereal captures
> > > on Host2. All these
> > > messages are going through the proxy server(195.37.77.99).
> > >
> > > Can someone please tell me why the proxy server is behaving this
> > > way, i.e. sending ACK on 5060
> > > instead of the contact. Is there anything that i am missing
> > > here or doing
> > > wrong.
> > >
> > > Thanks
> > > Mahesh
> > >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
> > >
>
Can some one help even when I try from the CLI tool:
serctl alias add newman sip:newman@<domain>
sip:newman@<domain>
400 Table 'aliases' not found in memory, use save("aliases") or
lookup("aliases"
) in the configuration script first
And I do have the alias configured under the CFG file!
# All REGISTER attempts are processed and must always be authenticated
if (method=="REGISTER") {
# make sure that users don't register infinite loops
if (search("^(Contact|m): .*(a)(10\.1\.2\.3|(proxy\.)?bigu\.edu)")) {
log(1, "LOG: alert: someone trying to set aor==contact\n");
sl_send_reply("476", "No Server Address in Contacts Allowed" );
break;
};
# challenge/response
if (!www_authorize("<Domain>", "subscriber")) {
www_challenge("<Domain>", "0");
break;
};
# only registered users are allowed
if (!is_user("replicator") & !check_to()) {
log(1, "LOG: unregistered user registration attempt\n");
sl_send_reply("403", "Only registered users are allowed");
break;
};
# it is an authenticated request, update Contact database now
if (!save("location")) {
sl_reply_error();
};
break;
};
# process traffic local to BigU and the PSTN
# Find the canonical username
lookup("aliases");
Shiran Guez
I believe that we have identified a bug in SER related to limitations in
the size of the SIP message SER will t_relay. This bug is easily
reproducible and is described as follows:
Infrastructure description:
Internet <-> SER/rtpproxy 8.14 <-> Asterisk SIP2PSTN GW
1.) In my setup, I am using Asterisk as a SIP2PSTN gateway.
2.) Asterisk is deployed on a non-routable address segment.
3.) I have SER/rtpproxy 8.14 deployed on an internet routable
segment.
4.) Users register to SER at the DMZ border.
5.) When a user makes a telephone call, SER t_relay's the INVITE in
Asterisk
6.) During call setup, rtpproxy is used to connect rtp from the
caller to the Asterisk GW.
Problem description:
With the current setup, a user can take a phone such as a Cisco 7960 or
Xten soft phone and successfully register, make calls, and receive
calls. These clients may be behind NAT firewalls. SER is resolving NAT
configuration issues with the assistance of the NAThelper module.
Recently, we began testing with products from Ingate and Jasomi.
Customers are intent on using these vendor supplied solutions to enable
UA's hosted on their corporate intranets to access external sip
services. Each solution is deployed in a similar manner. This
architecture is described as follows:
1.) An Ingate or Jasomi is deployed on an internet routable segment.
2.) A second ingate or Jasomi is deployed on a non-routable intranet
facing segment.
3.) An ipsec tunnel is constructed between the two ingates.
In this segment, UA's on the intranet use the intranet Ingate or Jasomi
as a standard SIP proxy to access external SIP services. To facilitate
this, both are configured in a "hard forward" manner to push SIP traffic
across the ipsec tunnel to the seconds Ingate or Jasomi. We have
successfully registered from the intranet to our internet facing SER
implementation through this setup. We are also able to make calls from
our intranet through this proxy setup internet facing 3rd party SIP end
points. However, when we attempt to send an INVITE to our SER/rtpproxy
infrastructure, SER truncates the INVITE when it is forwarded to our
Asterisk GW. Asterisk follows through with the INVITE process and will
ring the intended phone. However, when the called party answers,
Asterisk is unable to complete call setup because the "a" and "m"
parameters are missing from the SDP. At this point the called party is
dropped and the Ingate and the UA are left waiting for the RTP or a BYE
that never comes.
>From our observation, this problem is due to the size of the SIP INVITE,
which is sent to SER. Both Ingate and Jasomi create additional VIA
parameters in the SIP INVITE in order to store state information. This
state information is stored in encrypted strings in the xdata field of
the VIA. It seems that the addition of these VIA fields increases the
size of the SIP message beyond the SER's limits causing truncation upon
relay. When the INVITE is t_relay'ed, much of the SDP is missing.
Please see the following ngrep of the SIP INVITE being relayed. I have
replaced all pertinent address information for our own disclosure
purposes.
______________________________________________
Device list:
Ingate: 10.1.1.1
SER: 10.2.2.2/sbc1.mydomain.com
Xten UA: 10.3.3.3
Asterisk gw: 10.4.4.4
##
U 10.1.1.1:5060 -> 10.2.2.2:5060
INVITE sip:16179086547@sbc1.mydomain.com SIP/2.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK8d1c8a92109d8a370c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK94ce1c153879cbc60c7f7299b985c8f4.0;xdata=UkrU+mWJL
aKZXFCdTMwK3YcFmw9BXXO0mZ-oXaK-fZQ_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bKA3614A811BC64CCB8E74944E08E28F13;rport=35060;branc
h=z9hG4bKA3614A811BC64CCB8E74944E08E28F13;xdata=8BnRlTLlFQxaEMygbWSMP79K
bMGMDOh+FcKZmz3mvlR09UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>.
Contact:
<sip:esF1vz2EczTjGzG7n6VSFaJSXkL7bF2zwIo3bfnGcryex2fyUkto0gwwTTREPunT71-
RsgM6xtWrz8Yc_PUuyGwcHdfV0OieldqEwsaPMEJLsA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12666 INVITE.
Max-Forwards: 68.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:eDpENJ1vtGdOGot7umZmcMs7cLQcpirjPwNAsYLWoPXQlOnCIQZXXwov084odkZ_h@1
0.1.1.1;lr>.
Content-Length: 230.
.
v=0.
o=6173164000 94360252 94360262 IN IP4 10.1.1.1.
s=X-Lite.
c=IN IP4 10.1.1.1.
t=0 0.
m=audio 58192 RTP/AVP 0 8 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:8 pcma/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-15.
#
U 10.2.2.2:5060 -> 10.1.1.1:5060
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK8d1c8a92109d8a370c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK94ce1c153879cbc60c7f7299b985c8f4.0;xdata=UkrU+mWJL
aKZXFCdTMwK3YcFmw9BXXO0mZ-oXaK-fZQ_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bKA3614A811BC64CCB8E74944E08E28F13;rport=35060;branc
h=z9hG4bKA3614A811BC64CCB8E74944E08E28F13;xdata=8BnRlTLlFQxaEMygbWSMP79K
bMGMDOh+FcKZmz3mvlR09UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To:
<sip:16179086547@sbc1.mydomain.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58
.6c1d.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12666 INVITE.
Proxy-Authenticate: Digest realm="sbc1.mydomain.com",
nonce="4140d569a58f4230a925f11b564c223a856b792a".
Server: Sip EXpress router (0.8.14 (i386/linux)).
Content-Length: 0.
Warning: 392 10.2.2.2:5060 "Noisy feedback tells: pid=26357
req_src_ip=10.1.1.1 req_src_port=5060
in_uri=sip:16179086547@sbc1.mydomain.com
out_uri=sip:16179086547@sbc1.mydomain.com via_cnt==3".
.
#
U 10.1.1.1:5060 -> 10.2.2.2:5060
ACK sip:16179086547@sbc1.mydomain.com SIP/2.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK8d1c8a92109d8a370c7f7299b985c8f4.0.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To:
<sip:16179086547@sbc1.mydomain.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58
.6c1d.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12666 ACK.
Content-Length: 0.
.
#
U 10.1.1.1:5060 -> 10.2.2.2:5060 15763@0:1480
.......0INVITE sip:16179086547@sbc1.mydomain.com SIP/2.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>.
Contact:
<sip:e2AyJyUQgCGf_Y06tu_rM3e-U3sthj-vO8pYWVWTJVaikNLrDMx5XcCCLEBXvjyirBs
hBuEUU_feciI091Ig8MNh7KZJzeH1d4fC7EsItfCfsA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
Proxy-Authorization: Digest
username="6173164000",realm="sbc1.mydomain.com",nonce="4140d569a58f4230a
925f11b564c223a856b792a",response="e9a140cc3bad75e35c6a96449ff7cc41",uri
="sip:16179086547@sbc1.mydomain.com".
Max-Forwards: 68.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:e7DlN09kmHaZbabZRm9W0bzJ0uoyUyFM0PVyKvgCloKvDqsLXMsCA6nvRkR8LsbRi@1
0.1.1.1;lr>.
Content-Length: 230.
.
v=0.
o=6173164000 94360252 94360262 IN IP4 10.1.1.1.
s=X-Lite.
c=IN IP4 10.1.1.1.
t=0 0.
m=audio 58194 RTP/AVP 0 8 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:8 pcma
#
U 10.2.2.2:5060 -> 10.1.1.1:5060
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
Server: Sip EXpress router (0.8.14 (i386/linux)).
Content-Length: 0.
Warning: 392 10.2.2.2:5060 "Noisy feedback tells: pid=26356
req_src_ip=10.1.1.1 req_src_port=5060
in_uri=sip:16179086547@sbc1.mydomain.com
out_uri=sip:16179086547@10.4.4.4:5060 via_cnt==3".
.
#
U 10.2.2.2:5060 -> 10.4.4.4:5060 64701@0:1480
.......qINVITE sip:16179086547@10.4.4.4:5060 SIP/2.0.
Record-Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Via: SIP/2.0/UDP 10.2.2.2;branch=z9hG4bKa01f.bbf787d1.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>.
Contact:
<sip:e2AyJyUQgCGf_Y06tu_rM3e-U3sthj-vO8pYWVWTJVaikNLrDMx5XcCCLEBXvjyirBs
hBuEUU_feciI091Ig8MNh7KZJzeH1d4fC7EsItfCfsA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
Proxy-Authorization: Digest
username="6173164000",realm="sbc1.mydomain.com",nonce="4140d569a58f4230a
925f11b564c223a856b792a",response="e9a140cc3bad75e35c6a96449ff7cc41",uri
="sip:16179086547@sbc1.mydomain.com".
Max-Forwards: 67.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:e7DlN09kmHaZbabZRm9W0bzJ0uoyUyFM0PVyKvgCloKvDqsLXMsCA6nvRkR8LsbRi@1
0.1.1.1;lr>.
Content-Length: 230.
.
v=0.
o=6173164000 94360252 94360262 I
#
U 10.2.2.2:5060 -> 10.4.4.4:5060 64702@0:1480
.......qINVITE sip:16179086547@10.4.4.4:5060 SIP/2.0.
Record-Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Via: SIP/2.0/UDP 10.2.2.2;branch=z9hG4bKa01f.bbf787d1.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>.
Contact:
<sip:e2AyJyUQgCGf_Y06tu_rM3e-U3sthj-vO8pYWVWTJVaikNLrDMx5XcCCLEBXvjyirBs
hBuEUU_feciI091Ig8MNh7KZJzeH1d4fC7EsItfCfsA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
Proxy-Authorization: Digest
username="6173164000",realm="sbc1.mydomain.com",nonce="4140d569a58f4230a
925f11b564c223a856b792a",response="e9a140cc3bad75e35c6a96449ff7cc41",uri
="sip:16179086547@sbc1.mydomain.com".
Max-Forwards: 67.
Content-Type: application/sdp.
User-Agent: X-Lite release 1103m.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:e7DlN09kmHaZbabZRm9W0bzJ0uoyUyFM0PVyKvgCloKvDqsLXMsCA6nvRkR8LsbRi@1
0.1.1.1;lr>.
Content-Length: 230.
.
v=0.
o=6173164000 94360252 94360262 I
#
U 10.4.4.4:5060 -> 10.2.2.2:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 10.2.2.2;branch=z9hG4bKa01f.bbf787d1.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
User-Agent: Asterisk PBX.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER.
Contact: <sip:16179086547@10.4.4.4>.
Content-Length: 0.
.
#
U 10.4.4.4:5060 -> 10.2.2.2:5060
SIP/2.0 183 Session Progress.
Via: SIP/2.0/UDP 10.2.2.2;branch=z9hG4bKa01f.bbf787d1.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
User-Agent: Asterisk PBX.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER.
Contact: <sip:16179086547@10.4.4.4>.
Content-Type: application/sdp.
Content-Length: 259.
.
v=0.
o=root 4025 4025 IN IP4 10.4.4.4.
s=session.
c=IN IP4 10.4.4.4.
t=0 0.
m=audio 19052 RTP/AVP 3 0 8 101.
a=rtpmap:3 GSM/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=silenceSupp:off - - - -.
#
U 10.2.2.2:5060 -> 10.1.1.1:5060
SIP/2.0 183 Session Progress.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
User-Agent: Asterisk PBX.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER.
Contact: <sip:16179086547@10.4.4.4>.
Content-Type: application/sdp.
Content-Length: 259.
.
v=0.
o=root 4025 4025 IN IP4 10.4.4.4.
s=session.
c=IN IP4 10.4.4.4.
t=0 0.
m=audio 19052 RTP/AVP 3 0 8 101.
a=rtpmap:3 GSM/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=silenceSupp:off - - - -.
####
U 10.4.4.4:5060 -> 10.2.2.2:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 10.2.2.2;branch=z9hG4bKa01f.bbf787d1.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
Record-Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:e7DlN09kmHaZbabZRm9W0bzJ0uoyUyFM0PVyKvgCloKvDqsLXMsCA6nvRkR8LsbRi@1
0.1.1.1;lr>.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
User-Agent: Asterisk PBX.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER.
Contact: <sip:16179086547@10.4.4.4>.
Content-Type: application/sdp.
Content-Length: 259.
.
v=0.
o=root 4025 4026 IN IP4 10.4.4.4.
s=session.
c=IN IP4 10.4.4.4.
t=0 0.
m=audio 19052 RTP/AVP 3 0 8 101.
a=rtpmap:3 GSM/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=silenceSupp:off - - - -.
#
U 10.2.2.2:5060 -> 10.1.1.1:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK080E9671A10348788D72788ABB32E000;rport=35060;branc
h=z9hG4bK080E9671A10348788D72788ABB32E000;xdata=g8U1gLW+1SbzScgzuAlduOZY
SyicHJNYp0Htso2oJc909UTlKI5NKdRfAsMB1v-2.
Record-Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Record-Route: <sip:dd4f232@10.1.1.1;lr>.
Record-Route:
<sip:e7DlN09kmHaZbabZRm9W0bzJ0uoyUyFM0PVyKvgCloKvDqsLXMsCA6nvRkR8LsbRi@1
0.1.1.1;lr>.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 INVITE.
User-Agent: Asterisk PBX.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER.
Contact: <sip:16179086547@10.4.4.4>.
Content-Type: application/sdp.
Content-Length: 259.
.
v=0.
o=root 4025 4026 IN IP4 10.4.4.4.
s=session.
c=IN IP4 10.4.4.4.
t=0 0.
m=audio 19052 RTP/AVP 3 0 8 101.
a=rtpmap:3 GSM/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=silenceSupp:off - - - -.
#
U 10.1.1.1:5060 -> 10.2.2.2:5060
ACK sip:16179086547@10.4.4.4 SIP/2.0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK8A5B0DBACBFA421DBE4F707FA2084744;rport=35060;branc
h=z9hG4bK8A5B0DBACBFA421DBE4F707FA2084744;xdata=qDJF1BWCnmazyv84YkNW+wqO
ln1crB-OMdLqm-1dScJ09UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Contact:
<sip:e5oUfTi8xf2OqFiDy7UfeA7DqUjH00lIfqT4fsKAkukUTt1duZ_VPH2tfjJwa_F0yN4
ZoQcfeXYHJG2YatOPWrhtr0LX4ucrckG00r17249_sA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 ACK.
Max-Forwards: 68.
Content-Length: 0.
.
#
U 10.2.2.2:5060 -> 10.4.4.4:5060
ACK sip:16179086547@10.4.4.4 SIP/2.0.
Record-Route: <sip:16179086547@10.2.2.2;ftag=4167926089;lr=on>.
Via: SIP/2.0/UDP 10.2.2.2;branch=0.
Via: SIP/2.0/UDP
10.1.1.1:5060;branch=z9hG4bK3fb33a2d10203ada0c7f7299b985c8f4.0.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK4afb43404e7c33130c7f7299b985c8f4.0;xdata=Ly0nkoyID
7sZ1hOYXRKnV3gFIgkEphTIhD00WmRnWSo_.
Via: SIP/2.0/UDP
0.0.0.0;branch=z9hG4bK8A5B0DBACBFA421DBE4F707FA2084744;rport=35060;branc
h=z9hG4bK8A5B0DBACBFA421DBE4F707FA2084744;xdata=qDJF1BWCnmazyv84YkNW+wqO
ln1crB-OMdLqm-1dScJ09UTlKI5NKdRfAsMB1v-2.
From: Test User <sip:6173164000@sbc1.mydomain.com:35060>;tag=4167926089.
To: <sip:16179086547@sbc1.mydomain.com>;tag=as3b7f7d4e.
Contact:
<sip:e5oUfTi8xf2OqFiDy7UfeA7DqUjH00lIfqT4fsKAkukUTt1duZ_VPH2tfjJwa_F0yN4
ZoQcfeXYHJG2YatOPWrhtr0LX4ucrckG00r17249_sA5in1v1fKYFFWpWOtqrj(a)10.1.1.1>
.
Call-ID: 537E6EED-0DCD-4DDF-AE66-EDCC8A95DC79(a)10.3.3.3.
CSeq: 12667 ACK.
Max-Forwards: 67.
Content-Length: 0.
.
After this ACK is relayed, the call setup is incomplete because asterisk
has dropped the call.
__________________________________________
Salvatore Giudice
617-392-1689
617-392-8120
salvatore.giudice(a)fmr.com
See my post...
Good luck
Gwen
---------------------------- Message original ----------------------------
Objet: RE: [Serusers] could not open module mysql.so
De: g.billoudet(a)arwen-tech.fr
Date: Ven 10 septembre 2004 15:04
À: g.billoudet(a)arwen-tech.fr
Copie à: "Zeus Ng" <zeus.ng(a)isquare.com.au>
serusers(a)lists.iptel.org
--------------------------------------------------------------------------
I finally found the solution...
First, I don't know why but I had a strange link file
(libmysqlclient.so.10) in my folder /usr/local/lib/ser/modules. I deleted
it and then I got the following result of the command "ldd mysql.so" :
linux-gate.so.1 => (0xffffe000)
libmysqlclient.so.10 => /usr/lib/libmysqlclient.so.10 (0x40028000)
libz.so.1 => /usr/lib/libz.so.1 (0x4005f000)
libc.so.6 => /lib/tls/libc.so.6 (0x40070000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x401b8000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401e5000)
libm.so.6 => /lib/tls/libm.so.6 (0x401f8000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
Now, I have the same result than Zeus but I didn't have any
/usr/lib/libmysqlclient.so.10...
When I installed the libmysql12, I obtained new files in /usr/lib/
(libmysqlclient.so.12 and some others). When SER try to load mysql.so, it
looks for the library libmysqlclient.so.10 and obviously can't find it. So
I made a link with the following command :
ln -s libmysqlclient.so.12 libmysqlclient.so.10
And now, SER can load the mysql module !!
Thanks for your help Zeus !!
Bye, Gwen
>
> Hi Zeus and other serusers,
>
> The mysql.so file is the one I got with
SER.(ser-0.8.12_linux_i386.tar.gz, if I remember...).
>
> Could you tell me what output you get with this command :
> # ldconfig -v |grep mysql
> ldconfig: Path `/usr/lib' given more than once
> libmysqlclient_r.so.12 -> libmysqlclient_r.so.12.0.0
> libmysqlclient.so.12 -> libmysqlclient.so.12.0.0
> libmysqlclient.so.10 -> libmysqlclient.so.10
>
> Thanks,
> Gwen
>
>
>
>> Gwen,
>>
>> There is something wrong with your mysql.so file. Did you compile it
yourself or download it somewhere? It doesn't look like mysql library
is linked into it. My ldd output is like this:
>>
>> sip:/usr/local/lib/ser/modules> ldd mysql.so
>> libmysqlclient.so.10 => /usr/lib/libmysqlclient.so.10
>> (0x00bbb000)
>> libz.so.1 => /usr/lib/libz.so.1 (0x00abf000)
>> libc.so.6 => /lib/tls/libc.so.6 (0x003f3000)
>> libcrypt.so.1 => /lib/libcrypt.so.1 (0x0056a000)
>> libnsl.so.1 => /lib/libnsl.so.1 (0x0029e000)
>> libm.so.6 => /lib/tls/libm.so.6 (0x00111000)
>> libnss_files.so.2 => /lib/libnss_files.so.2 (0x00a7d000)
libnss_dns.so.2 => /lib/libnss_dns.so.2 (0x006dd000)
>> libresolv.so.2 => /lib/libresolv.so.2 (0x00967000)
>> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0036b000)
>>
>> Note the first line states that mysql.so should dynamically load the mysql
>> library from /usr/lib/libmysqlclient.so.10. It is absent from your output.
>> Either recompile the module or download another copy from the FTP server.
>>
>> Zeus
>>
>>> -----Original Message-----
>>> From: g.billoudet(a)arwen-tech.fr [mailto:g.billoudet@arwen-tech.fr]
Sent: Friday, 10 September 2004 5:10 PM
>>> To: Zeus Ng
>>> Cc: serusers(a)lists.iptel.org
>>> Subject: RE: [Serusers] could not open module mysql.so
>>>
>>>
>>> Thank you for your help Zeus,
>>>
>>> Here are the output of the commands :
>>>
>>> [root@linux gwen]# ldd /usr/local/lib/ser/modules/mysql.so
>>> linux-gate.so.1 => (0xffffe000)
>>> libz.so.1 => /usr/lib/libz.so.1 (0x40028000)
>>> libc.so.6 => /lib/tls/libc.so.6 (0x40039000)
>>> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
>>>
>>> [root@linux gwen]# cat /etc/ld.conf
>>> cat: /etc/ld.conf: No such file or directory
>>>
>>> [root@linux gwen]# cat /etc/ld.so.conf
>>> /usr/X11R6/lib
>>> /usr/lib/qt3/lib
>>> /usr/local/lib/ser/modules
>>> /usr/lib
>>>
>>> Gwen
>>>
>>>
>>> > Gwen,
>>> >
>>> > It appears that your mysql.so is not link properly with the mysql
library. Send the following output to the list. It may give us more
insight on your problem.
>>> >
>>> > root# ldd /usr/local/lib/ser/modules/mysql.so
>>> > root# cat /etc/ld.conf
>>> >
>>> >
>>> > Zeus
>>> >
>>> >> -----Original Message-----
>>> >> From: serusers-bounces(a)lists.iptel.org
>>> [mailto:serusers-bounces@lists.iptel.org]
>>> >> On Behalf Of g.billoudet(a)arwen-tech.fr
>>> >> Sent: Friday, 10 September 2004 12:46 AM
>>> >> To: g.billoudet(a)arwen-tech.fr
>>> >> Cc: serusers(a)lists.iptel.org
>>> >> Subject: Re: [Serusers] could not open module mysql.so
>>> >>
>>> >>
>>> >>
>>> >> Hi,
>>> >>
>>> >> I checked my MySQL-client package. So I installed
>>> >> MySQL-client-4.0.20-0.i386.rpm. I also had to install the package
libmysql12. But, I still have the same problem with the
>>> load of mysql
>>> >> module...
>>> >>
>>> >> I the folder /usr/lib, new files appeared : libmysqlclient_r.so.12@
libmysqlclient_r.so.12.0.0*
>>> >> libmysqlclient.so.10*
>>> >> libmysqlclient.so.12@
>>> >> libmysqlclient.so.12.0.0*
>>> >>
>>> >> What 'libmysqlclient' files do you have in your folder
>>> /usr/lib and
>>> >> /usr/local/lib/ser/modules/ ??
>>> >>
>>> >> When I use "/usr/local/sbin/ser -c", the message of the error is a
bit different :
>>> >> 0(2570) loading module /usr/local/lib/ser/modules/mysql.so 0(2570)
ERROR: load_module: could not open module
>>> >> </usr/local/lib/ser/modules/mysql.so>:
>>> >> /usr/local/lib/ser/modules/mysql.so: undefined symbol:
>>> >> mysql_field_count
>>> >> 0(2570) parse error (14,13-49): failed to load module
>>> >> # ...bla bla... don't mind
>>> >> ERROR: bad config file (1 errors)
>>> >>
>>> >>
>>> >> Thanks for help
>>> >> Gwen
>>> >>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>
>>
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
Hi,
I am just getting started with SER, and I'm trying to adapt the sample
.pstn.cfg to allow IP-IP calls for numbers that begin with 8.
Can someone please give me a pointer as to how to do this, as no matter
what I try, the thing seems to insist on trying to send the call to my
gateway.
thanks
jamie.
--