sr-users

sr-users@lists.kamailio.org

37 participants
37547 discussions

Start a nNew thread

[Users] Openser accounting
by Lucas Diaz 20 Apr '07

20 Apr '07

Is it possible to save call length? Why can't I save BYE methods? Thanks.

2 1

[Users] radius accounting
by Terry Robert 19 Apr '07

19 Apr '07

Dear Openser, After some investigation, I discovered that the radius accounting behavior is different between openser-1.2.0-tls, and openser-1.1.1-tls. Specifically, when running the basic UAS/UAC scenario in SIPp, I observe the following: 1) Openser-1.1.1-tls - generates 2 accounting start packets, 1 accounting stop. User-Name, CalledStationId, CallingStationId attributes are present. 2) Openser-1.2.0-tls - generates 1 accounting start packet, 1 accounting stop. User-Name, CalledStationdId, CallingStationId attributes are missing. Can anyone: 1) confirm this behaviour? 2) tell me which one is correct? Thank you for your assistance in this matter.

3 2

[Users] symmetric firewall without nat
by Alexander Bergolth 19 Apr '07

19 Apr '07

Hi! In our organization there are many subnets with public-ip-adresses that are behind stateful-firewalls that prevent incoming connections from outside. If the clients are in two different protected subnets, they won't be able to communicate without an rtpproxy. Unfortunately since there is no NAT involved, the nat_uac_test() won't be useful. Is there any other way for the server to detect that an rtpproxy has to be used? Is there a way for the clients to detect it and report it to the server? Thanks in advance, --leo -- ----------------------------------------------------------------------- Alexander.Bergolth (at) wu-wien.ac.at Fax: +43-1-31336-906050 Zentrum fuer Informatikdienste - Wirtschaftsuniversitaet Wien - Austria

2 1

[Users] block calls
by Carlos Ribas 19 Apr '07

19 Apr '07

I need to block calls that they start with number 0. i did this, but it`s not OK: if (uri=~"^sip:[1-9]*@.*") { rewritehost("10.0.0.10"); log("access ok"); route(1); break; }; if (uri=~"^sip:0[1-9]*@.*") { log("access deny"); break; }; How can i do this?

2 2

[Users] TLS communication between OpenSER servers
by John Barry 19 Apr '07

19 Apr '07

Hi, I have configured two SIP domains using OpenSER v 1.1.1 with authentication (digest authentication) and TLS support. Each domain has clients (UAC) running minisip (3220) with TLS and certificates configured. When there is a call between a user from one domain to a user in the other domain, the SIP communications between minisip clients and their corresponding OpenSER proxies is done via TLS (port 5061/TCP), however, the SIP communication between the two OpenSER proxies is still done via UDP (port 5060/UDP). The TLS configuration in both servers is as follows: disable_tls = 0 listen = tls:192.168.1.10:5061 tls_verify_server = 1 tls_verify_client = 1 tls_require_client_certificate = 1 tls_method = TLSv1 tls_certificate = "/etc/openser/tls/sipdA/sipdA-cert.pem" tls_private_key = "/etc/openser/tls/sipdA/sipdA-privkey.pem" tls_ca_list = "/etc/openser/tls/sipdA/sipdA-calist.pem" Any ideas or suggestions regarding how to enable SIPS (TLS) between OpenSER SIP proxies? Thanks. JB74 _________________________________________________________________ Live Search, for accurate results! http://www.live.nl

2 1

[Serusers] Ser as IVR
by Arun Kumar 19 Apr '07

19 Apr '07

Hi, Is it possible to design an IVR using SER ? If yes please advice. thanks arun

2 1

[Users] Serweb + OpenSER 1.2.0 with postgres
by Joao Pereira 19 Apr '07

19 Apr '07

Hello is someone using serweb with OpenSER 1.2.0 and postgres? I want to know if it is possible. I tried the version in http://voip-info.org/wiki/view/OpenSER+1.1.x+and+SerWEB+0.9.4 but it isn't working and this error happens: Function aggregate_methods() doesn't exists. Try install Classkit extension. http://pecl.php.net/package/classkit I already tried classkit and the problem remains. Is someone using serweb + OpenSER 1.2.0 + postgres? Thanks regards Joao Pereira -- ______________________________________________ João Gomes Pereira FCCN Av. do Brasil, nº 101 1700-066 Lisboa tel: +351 218 440 100 - fax: +351 218 472 167 email|SIP: joao.pereira(a)fccn.pt http://www.fccn.pt ______________________________________________ --- Aviso de Confidencialidade Esta mensagem é exclusivamente destinada ao seu destinatário, podendo conter informação CONFIDENCIAL, cuja divulgação está expressamente vedada nos termos da lei. Caso tenha recepcionado indevidamente esta mensagem, solicitamos-lhe que nos comunique esse mesmo facto por esta via ou para o telefone +351 218 440 100 devendo apagar o seu conteúdo de imediato. This message is intended exclusively for its addressee. It may contain CONFIDENTIAL information protected by law. If this message has been received by error, please notify us via e-mail or by telephone +351 218 440 100 and delete it immediately. ---

2 2

Re: [Users] openser + nathelper + rtpproxy w/ ekiga
by Ben Racher 19 Apr '07

19 Apr '07

openser is not behind my NAT (see the dump, it has a public IP), wouldn't that defeat the purpose of nathelper? one of my clients is behind the NAT, the other isn't. some of the SDP flags appear to be correct, but I myself am still new enough to SIP that i can't tell what my SDP flags should be like coming out of the openser box. it appears to be correct, could you please take a look at the dump and tell me what specific transactions are causing it to fail? ben raviprakash sunkara wrote: > Hi > did U Check the sdp flags, nathelper modules in fixed_nated_sdp and > force_rtp_proxy flag,,,,,,, > > time interval to alive the natter.............. > > > is ur OpenSER is Behind the NAT, and Urs Users are also in Behind NAT > > > > On 4/19/07, *Ben Racher* <mack.stout(a)gmail.com > <mailto:mack.stout@gmail.com>> wrote: > > I'm trying to use openser's (1.1.1) default nathelper.cfg to > connect two > ekiga clients. One is behind a NAT. Both can contact each other, > but the > media streams (neither video nor audio) don't seem to be setup for > some > reason. rtpproxy registers that it should setup the connection, but it > doesn't seem to take off past that. > > here's an ngrep dump of the NAT'd client calling the other, and could > appreciate some wisdom on what I need to fix and what the problem is. > thanks. > > -------- > > U 2006/04/20 00:11:09.663917 209.91.15.175:5071 > <http://209.91.15.175:5071> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > INVITE sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110> SIP/2.0. > Date: Thu, 19 Apr 2007 04:44:30 GMT. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport. > > User-Agent: Ekiga/2.0.3. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110>>. > Contact: <sip:test_store@192.168.0.25:5071;transport=udp>. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Type: application/sdp. > Content-Length: 227. > Max-Forwards: 70. > . > v=0. > o=- 1176957870 1176957870 IN IP4 192.168.0.25 <http://192.168.0.25>. > s=Opal SIP Session. > c=IN IP4 192.168.0.25 <http://192.168.0.25>. > t=0 0. > m=audio 5006 RTP/AVP 101. > a=rtpmap:101 telephone-event/8000. > a=fmtp:101 0-15. > m=video 5008 RTP/AVP 31. > a=rtpmap:31 H261/90000. > > > U 2006/04/20 00:11:09.673012 209.91.15.110:5060 > <http://209.91.15.110:5060> -> 209.91.15.175:5071 > <http://209.91.15.175:5071> > SIP/2.0 100 trying -- your call is important to us. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071;received=209.91.15.175 > <http://209.91.15.175>. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: < sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110>>. > Server: OpenSer (1.1.1-notls (i386/linux)). > Content-Length: 0. > Warning: 392 209.91.15.110:5060 <http://209.91.15.110:5060> "Noisy > feedback tells: pid=4047 > req_src_ip= 209.91.15.175 <http://209.91.15.175> req_src_port=5071 > in_uri=sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110> > out_uri=sip:test@209.91.15.19:5074;transport=udp via_cnt==1". > . > > > U 2006/04/20 00:11:09.673822 209.91.15.110:5060 > <http://209.91.15.110:5060> -> 209.91.15.19:5074 > <http://209.91.15.19:5074> > INVITE sip:test@209.91.15.19:5074;transport=udp SIP/2.0. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > Date: Thu, 19 Apr 2007 04:44:30 GMT. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;received=209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > > User-Agent: Ekiga/2.0.3. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110>>. > Contact: <sip:test_store@209.91.15.175:5071;transport=udp>. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Type: application/sdp. > Content-Length: 270. > Max-Forwards: 69. > P-hint: usrloc applied. > . > v=0. > o=- 1176957870 1176957870 IN IP4 192.168.0.25 <http://192.168.0.25>. > s=Opal SIP Session. > c=IN IP4 209.91.15.110 <http://209.91.15.110>. > t=0 0. > m=audio 35000 RTP/AVP 101. > a=rtpmap:101 telephone-event/8000. > a=fmtp:101 0-15. > m=video 35002 RTP/AVP 31. > a=rtpmap:31 H261/90000. > a=direction:active. > a=nortpproxy:yes. > > > U 2006/04/20 00:11:09.678496 209.91.15.19:5074 > <http://209.91.15.19:5074> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > SIP/2.0 100 Trying. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0. > Via: SIP/2.0/UDP > 192.168.0.25:5071 <http://192.168.0.25:5071>;received= > 209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110>>. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Length: 0. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > > > U 2006/04/20 00:11:09.801370 209.91.15.19:5075 > <http://209.91.15.19:5075> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > SIP/2.0 100 Trying. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;received=209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Length: 0. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > > > U 2006/04/20 00:11:09.824859 209.91.15.19:5075 > <http://209.91.15.19:5075> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > SIP/2.0 502 Bad Gateway. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0 . > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;received=209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Length: 0. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > > > U 2006/04/20 00:11:09.827826 209.91.15.110:5060 > <http://209.91.15.110:5060> -> 209.91.15.19:5074 > <http://209.91.15.19:5074> > ACK sip:test@209.91.15.19:5074;transport=udp SIP/2.0. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > CSeq: 1 ACK. > User-Agent: OpenSer (1.1.1-notls (i386/linux)). > Content-Length: 0. > . > > > U 2006/04/20 00:11:09.828858 209.91.15.110:5060 > <http://209.91.15.110:5060> -> 209.91.15.175:5071 > <http://209.91.15.175:5071> > SIP/2.0 502 Bad Gateway. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;received=209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > From: "Test Store" > < sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Length: 0. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > > > U 2006/04/20 00:11:09.847970 209.91.15.175:5071 > <http://209.91.15.175:5071> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > ACK sip:test@209.91.15.110 <mailto:sip:test@209.91.15.110> SIP/2.0. > CSeq: 1 ACK. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Length: 0. > Max-Forwards: 70. > . > > > U 2006/04/20 00:11:10.209491 209.91.15.19:5075 > <http://209.91.15.19:5075> -> 209.91.15.110:5060 > <http://209.91.15.110:5060> > SIP/2.0 200 OK. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP 209.91.15.110 > <http://209.91.15.110>;branch=z9hG4bK393e.770a5756.0. > Via: SIP/2.0/UDP > 192.168.0.25:5071 > <http://192.168.0.25:5071>;received=209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: < sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > Contact: <sip:test@209.91.15.19:5075;transport=udp>. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Type: application/sdp. > Content-Length: 153. > Record-Route: > <sip:209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > v=0. > o=- 1176929527 1176929527 IN IP4 209.91.15.19 <http://209.91.15.19>. > s=Opal SIP Session. > c=IN IP4 209.91.15.19 <http://209.91.15.19>. > t=0 0. > m=video 5012 RTP/AVP 31. > a=rtpmap:31 H261/90000. > > > U 2006/04/20 00:11:10.210568 209.91.15.110:5060 > <http://209.91.15.110:5060> -> 209.91.15.175:5071 > <http://209.91.15.175:5071> > SIP/2.0 200 OK. > CSeq: 1 INVITE. > Via: SIP/2.0/UDP > 192.168.0.25:5071 <http://192.168.0.25:5071>;received= > 209.91.15.175 > <http://209.91.15.175>;branch=z9hG4bK9280b754-9eec-db11-9dcc-00187185e000;rport=5071. > From: "Test Store" > <sip:test_store@209.91.15.110 > <mailto:sip:test_store@209.91.15.110>>;tag=a84faa54-9eec-db11-9dcc-00187185e000. > > Call-ID: 3a45aa54-9eec-db11-9dcc-00187185e000(a)192.168.0.25 > <mailto:3a45aa54-9eec-db11-9dcc-00187185e000@192.168.0.25>. > To: <sip:test@209.91.15.110 > <mailto:sip:test@209.91.15.110>>;tag=0a37f656-5cec-db11-9452-001372710463. > > Contact: <sip:test@209.91.15.19:5075;transport=udp>. > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE. > Content-Type: application/sdp. > Content-Length: 173. > Record-Route: > <sip: 209.91.15.110 > <http://209.91.15.110>;lr=on;ftag=a84faa54-9eec-db11-9dcc-00187185e000>. > . > v=0. > o=- 1176929527 1176929527 IN IP4 209.91.15.19 <http://209.91.15.19>. > s=Opal SIP Session. > c=IN IP4 209.91.15.110 <http://209.91.15.110>. > t=0 0. > m=video 35004 RTP/AVP 31. > a=rtpmap:31 H261/90000. > a=nortpproxy:yes. > > > > _______________________________________________ > Users mailing list > Users(a)openser.org <mailto:Users@openser.org> > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > -- > Thanks and Regards > Ravi Prakash Sunkara > ravi.sunkara(a)hyperion-tech.com <mailto:ravi.sunkara@hyperion-tech.com> > M:+91 9985077535 > www.hyperion-tech.com <http://www.hyperion-tech.com> > Client and Parent company :- www.august-networks.com > <http://www.august-networks.com>

1 0

[Users] presence: dealing with publish
by Cesc 19 Apr '07

19 Apr '07

Hi, I am using openser1.2 If the presence module receives a PUBLISH: - without E-Tag, it gets stored and if needed, a NOTIFY is generated ... works for me. - with an E-tag, for which this openser has not seen the first PUB (the one without E-tag) ... it gets discarded/ignored? How is the e-tag used in processing publishes and then generating notifies? I ask this because in my (peculiar) setup with two openser's sending publish to each other, depending on the order I start the elements (2 phones, 2 opensers), I don't get always a working behavior: - if the opensers are running before the phones start ... no problem ... I guess as they see the PUB without e-tag, it all goes fine - if the boot order is : openser1 ... then phone 1 ... sometime after (enough to miss the first PUB without e-tag) ... openser2 ... then phone2 ... Phone 2 does not receive NOTIFYs of status changes from phone1, eventhough the PUBlish messages do get to openser2 ... but somehow, they get "discarded" ... Regards, Cesc

2 1

[Users] corrupted From with uac_replace_from in case of re-invite
by tele 19 Apr '07

19 Apr '07

Hi all, I'm occured in this problem already seen here: http://www.openser.org/pipermail/users/2006-March/003540.html My problem occured between two different UA and only in case of a Re-INVITE for a T.38 fax communication. Im' using openser 1.2.0. I'm doing some translation with From for a correct CLI screening. I'm also checked that the RR parameters are correctly mirrored. find attached here the debug.log and a network trace. thank you :tele

2 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users