sr-users July 2008

sr-users@lists.kamailio.org

147 participants
207 discussions

[OpenSER-Users] About Openser Message
by Ali Jawad 09 Jul '08

09 Jul '08

Hi All hi when I do a call on Openser it shows the following on my softphone CallStatus Message: 183 SESSION PROGRESS;Ringing-tone=TRUE; Can this message be changed, if so how? Thanks

1 0

[OpenSER-Users] INVITE NAT problem
by Juan Backson 09 Jul '08

09 Jul '08

Hi, I am working on getting my two SIP phones behind firewall to talk to each other. One client is SPA 921 and the other client is xlite; and I am force rport for all SIP requests from clients. When xlite sends a INVITE request to openser, openser tries to send to SPA 921, but the PORT is still 5060, instead of 22848. Therefore, Openser keeps resending INVITE to SPA 921 but never reaches it. Both linksys and xlite do send preiodic SUBSCRIBE/NOTIFY to Openser. Is there anything else I am missing? U 48.133.23.45:21395 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-683f775fdd79a93d-1--d 87543-;rport. Max-Forwards: 70. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF O. Content-Type: application/sdp. Supported: timer. User-Agent: X-Lite release 1011s stamp 41150. Content-Length: 371. . v=0. o=- 9 2 IN IP4 192.168.1.100. s=CounterPath X-Lite 3.0. c=IN IP4 192.168.1.100. t=0 0. m=audio 5416 RTP/AVP 107 119 100 106 0 105 98 8 101. a=fmtp:101 0-15. a=rtpmap:107 BV32/16000. a=rtpmap:119 BV32-FEC/16000. a=rtpmap:100 SPEEX/16000. a=rtpmap:106 SPEEX-FEC/16000. a=rtpmap:105 SPEEX-FEC/8000. a=rtpmap:98 iLBC/8000. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 48.133.200.20:5060 -> 48.133.23.45:21395 SIP/2.0 100 Giving a try. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-683f775fdd79a93d-1--d 87543-;rport=21395;received=48.133.23.45. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. . U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.200.20:5060 -> 48.133.23.45:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.23.45:5060 -> 48.133.200.20:5060 INVITE sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> SIP/2.0. Record-Route: <sip:48.133.200.20;lr=on;ftag=12709c02>. Via: SIP/2.0/UDP 48.133.200.20;branch=z9hG4bK0996.d020a552.0. Via: SIP/2.0/UDP 192.168.1.100:53722;received=48.133.23.45;branch=z9hG4bK-d8754 3-683f775fdd79a93d-1--d87543-;rport=21395. Max-Forwards: 69. Contact: <sip:2000@48.133.23.45:21395>. To: "1005"<sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=12709c02. Call-ID: MzRjM2RkZjQxNDk3ZjVjOTFhMzYyZmM0MThmODI3N2U.. CSeq: 1 INVITE. Session-Expires: 95. Min-SE: 90. Allow: INVITE, U 48.133.23.45:21395 -> 48.133.200.20:5060 SUBSCRIBE sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45> SIP/2.0. Via: SIP/2.0/UDP 192.168.1.100:53722;branch=z9hG4bK-d87543-d900ee1c55767008-1--d 87543-;rport. Max-Forwards: 70. Contact: <sip:2000@48.133.23.45:21395>. To: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>. From: "2000"<sip:2000@48.133.23.45 <sip%3A2000(a)48.133.23.45>>;tag=8b347a51. Call-ID: MzY3NGIwNTJlMWY5Njg2MmM5YmI1NTIxNTRjZjljYzM.. CSeq: 1 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INF O. Supported: timer. User-Agent: X-Lite release 1011s stamp 41150. Event: message-summary. Content-Length: 0. . U 48.133.23.45:22840 -> 48.133.200.20:5060 NOTIFY sip:48.133.23.45 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-2c2e52f6;rport. From: "1005" <sip:1005@48.133.23.45 <sip%3A1005(a)48.133.23.45> >;tag=a45646112863dco0. To: <sip:48.133.23.45>. Call-ID: ad4c4ce-bb2b86f4(a)192.168.1.101. CSeq: 1017 NOTIFY. Max-Forwards: 70. Event: keep-alive. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. . Any suggestion will be helpful. JB

3 2

[OpenSER-Users] [MediaProxy] Sessions ends ("did timeout") during the INVITE
by Iñaki Baz Castillo 09 Jul '08

09 Jul '08

Hi, I'm suffering an important issue with MediaProxy in calls from/to my carrier softswitch. Sometimes it seems that MediaProxy assigns a media port during the INVITE but it closes it inmediatelly, so the following 183 forces the creation of a different media port and obviously the media dies. It works perfectly for long days but some days it has those problems. Please, could you people help me in investigating if a problem in my OpenSer/MediaProxy? I have a detailed real example. This is what happens: --------------------------------------------------------------------------- 09:28:46 - INVITE Client -> OpenSer (audio: 192.168.1.203:10370) 09:28:46 - INVITE OpenSer -> gateway (audio: 88.99.3.10:60696) <-- MediaProxy set 60696 port but inmediatelly ends the session. 09:28:48 - 183 Gateway -> OpenSer (audio: 66.11.6.142:45734) 09:28:48 - 183 OpenSer -> Client (audio: 88.99.3.10:60698) <-- Wrong port, MediaProxy set 60698 port !!! 09:28:49 - 200 Gateway -> OpenSer (audio: 66.11.6.142:45734) 09:28:49 - 200 OpenSer -> Client (audio: 88.99.3.10:60704) <-- Wrong port, MediaProxy set 60704 port !!! --------------------------------------------------------------------------- This is the mediaproxy/proxydispatcher log. As you can see media port open during INVITE is inmediatelly closed WHY?): --------------------------------------------------------------------------------------- ### 09:28:46 - 9:28:46 openser-host proxydispatcher[31874]: request 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 192.168.1.203:10370:audio 88.99.1.192 sip.domain.net local 66.11.0.144 remote Domain=20-=20Asterisk=20PBX info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag: - 09:28:46 openser-host mediaproxy[31869]: request 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 192.168.1.203:10370:audio 88.99.1.192 sip.domain.net local 66.11.0.144 remote Domain=20-=20Asterisk=20PBX info=totag:,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60696 - 09:28:46 openser-host mediaproxy[31869]: execution time: 0.60 ms - 09:28:46 openser-host proxydispatcher[31874]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: '88.99.3.10 60696' - 09:28:46 openser-host proxydispatcher[31874]: execution time: 2.45 ms **************** ERROR: Why does it occur ??? *********************** - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed) - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ********************************************************************* ### 09:28:48 - 09:28:48 openser-host proxydispatcher[31874]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag:4d764120338220087992847 - 09:28:48 openser-host mediaproxy[31869]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=totag:4d764120338220087992847,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:48 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60698 - 09:28:48 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ### 09:28:58 - 09:28:58 openser-host proxydispatcher[31874]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag:4d764120338220087992847 - 09:28:58 openser-host mediaproxy[31869]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=totag:4d764120338220087992847,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:58 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60704 - 09:28:58 openser-host mediaproxy[31869]: execution time: 0.62 ms - 09:28:58 openser-host proxydispatcher[31874]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: '88.99.3.10 60704' - 09:28:58 openser-host proxydispatcher[31874]: execution time: 1.15 ms **************** ERROR: Why does it occur ??? *********************** - 09:28:59 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed) - 09:28:59 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ********************************************************************* ### 09:29:05 - 09:29:05 openser-host proxydispatcher[31874]: delete 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net info= - 09:29:05 openser-host mediaproxy[31869]: delete 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net info= --------------------------------------------------------------------------------------- I also attach the complete SIP capture of this real example, but I see nothing wrong in it. The question is: Why MediaProxy ends the session during the INVITE? why does it close the port? Thanks a lot for any help. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

1 1

[OpenSER-Users] Compiling / running Mediaproxy 2.0 on Debian Lenny
by jh＠tutpro.com 08 Jul '08

08 Jul '08

mediaproxy diapatcher works in ubuntu hardy, but not in lenny. the only difference i see is tls/python related versions is in python-gnutls: hardy: python-gnutls 1.1.4-1 lenny: python-gnutls 1.1.5-2 -- juha

2 4

Re: [OpenSER-Users] getting error while adding module to openser
by Bogdan-Andrei Iancu 08 Jul '08

08 Jul '08

Well, the error message is quite self explaining: *No such file or directory* check if the */usr/src/OpenSER/openser-1.2.0-tls/modules/pna.so *really exists. Regards, Bogdan suresh tattikota wrote: > > hi > i checked it in log file,i am getting these errors > > *ERROR: load_module: could not open module > </usr/src/OpenSER/openser-1.2.0-* > ** > *tls/modules/pna.so>: > /usr/src/OpenSER/openser-1.2.0-tls/modules/pna.so: cannot open shared > object file: No such file or directory > * > *openser: parse error (54,13-14): failed to load module* > > *ERROR: no version info in module > </usr/local/lib/openser/modules/pna.so>: > /usr/local/lib/openser/modules/pna.so: undefined symbol: module_version* > > * ERROR: no version info in module > </usr/local/lib/openser/modules/pna.so>: > /usr/local/lib/openser/modules/pna.so: undefined symbol: module_version > * > > > thank u > > > On 7/7/08, *Bogdan-Andrei Iancu* <bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>> wrote: > > Hi > > is tour openser starting or not? if not, look (eventually in > syslog) for any startup errors. > > Regards, > Bogdan > > suresh tattikota wrote: > > hi all > ** *this is the steps i followed to add module * > ** * i took one example module as exMod and this exMod sub > directory is in directory called /modules * > ** ** *1. created one makefile * > *2.one .c file with one printf statement , .h file for > corresponding .c file * > *3.and added loadmodule "exMod.so" in openser.cfg file then * > *4. i run the openser with * make prifix=/usr/local/ all and > make prifix=/usr/local/ install > 5 while i am running the openser it is not showing any thing > *the .c an .h file of my* *exMod are * > > *exMod.c:* > > void print_modname() > { > > printf("this is module name "); > } > > *exMod.h* > > void print_modname(); > > and my Makefile is : > > include ../../Makefile.defs > auto_gen= > NAME=exMod.so > DEFS+=-I$(LOCALBASE)/include > LIBS= > > include ../../Makefile.modules > > so please help me regarding this > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)lists.openser.org <mailto:Users@lists.openser.org> > http://lists.openser.org/cgi-bin/mailman/listinfo/users > > > >

1 0

[OpenSER-Users] Strange REGISTER problem
by mark morreny 08 Jul '08

08 Jul '08

Hi, I am experiencing a very strange problem with REGISTER. If my SIP client registers to Openser with openser's internal IP ( 192.168.1.104), then it works. But if the SIP client registers using Openser's public IP, it does not work. The 200K returned from Openser is different for each case. For the 1st case, my SIP client recognizes the 200 OK, but for the 2nd case, my SIP client will keep on sending another REGISTER upon receiving the 200 OK. Here are the two different 200 OK msg that Openser sends back to the client. U 192.168.1.104:5060 -> 192.168.1.100:44522 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.100:44522 ;branch=z9hG4bK-d87543-7e47d706ec23b831-1--d87543-;rport=44522. To: "1006"<sip:1006@192.168.1.104 <sip%3A1006(a)192.168.1.104> >;tag=329cfeaa6ded039da25ff8cbb8668bd2.b23f. From: "1006"<sip:1006@192.168.1.104 <sip%3A1006(a)192.168.1.104> >;tag=7e6bbb05. Call-ID: MGYyMjczODBmNTRkMzA3Y2JmZjk4ODM0MjkxOWI5ZDQ.. CSeq: 2 REGISTER. Contact: <sip:1006@192.168.1.100:16728;rinstance=d380362012deaf00>;expires=1909, <sip:1006@192.168.1.100:16727;rinstance=94567af350ff0cad>;expires=1870, <sip:1006@192.168.1.100:25572;rinstance=57a835af07252a9e>;expires=3286, < U 192.168.1.104:5060 -> 78.251.75.157:16156 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.1.100:2388 ;branch=z9hG4bK-d87543-f0701c5a1050361a-1--d87543-;rport=16156;received= 78.251.75.157. To: "1006"<sip:1006@58.251.75.157 <sip%3A1006(a)58.251.75.157> >;tag=329cfeaa6ded039da25ff8cbb8668bd2.b13f. From: "1006"<sip:1006@58.251.75.157 <sip%3A1006(a)58.251.75.157> >;tag=48233454. Call-ID: ZDVjODBlMjAxODQ5ZjAxYTRkYzRjYzUxMjY3YzAxNjk.. CSeq: 2 REGISTER. Contact: <sip:1006@192.168.1.100:16728;rinstance=d380362012deaf00>;expires=1493, <sip:1006@192.168.1.100:16727;rinstance=94567af350ff0cad>;expires=1454, <sip:1006@192.168.1.100:25572;rinstance=57a835af072 Any help will be greatly appreciated. Thanks, Mark

1 1

[OpenSER-Users] problem with linksys SPA 921
by Juan Backson 08 Jul '08

08 Jul '08

Hello I am using Linksys spa 921 to talk to openser. The problem I am having is that when the phone gets a 401 Unauthorized msg from Openser during REGISTER, instead of re-register with digest, it sends back another Unauthorized msg to openser. Does anyone know when this is happening? U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12>. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" <sip:1005@192.168.1.101:5060>;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. . U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12 >;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. . U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12 >;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395d9bbe456c575a7a45745b7ec760b372923". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. . U 43.34.342.12:16309 -> 43.43.22.124:5060 REGISTER sip:43.34.342.12 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK-aed7e028. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12>. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. Max-Forwards: 70. Contact: "1005" <sip:1005@192.168.1.101:5060>;expires=3600. User-Agent: Sipura/SPA921-4.1.10(b). Content-Length: 0. Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER. . U 43.43.22.124:5060 -> 43.34.342.12:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12 >;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. . U 43.34.342.12:5060 -> 43.43.22.124:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 192.168.1.101:5060 ;branch=z9hG4bK-aed7e028;received=43.34.342.12. From: "1005" <sip:1005@43.34.342.12>;tag=b19e671c4f6697beo0. To: "1005" <sip:1005@43.34.342.12 >;tag=329cfeaa6ded039da25ff8cbb8668bd2.60bb. Call-ID: 6e601902-41d31f68(a)192.168.1.101. CSeq: 23942 REGISTER. WWW-Authenticate: Digest realm="43.43.22.124", nonce="487395dd63fe51d4006fddeab235203120c8faca". Server: OpenSER (1.3.2-notls (i386/linux)). Content-Length: 0. . Any suggestion to solving this problem will be great. JB

3 2

[OpenSER-Users] Can't add user to Mysql DB
by Eliass Salim 08 Jul '08

08 Jul '08

I installed openser 1.3, now I loaded Mysql module and made the required changes in /etc/openser/openserctlrc file. When I run the command: openserctl add 100 100 100@localhost I get the follwoing error: ERROR 1054 (42S22) at line 1: Unknown column 'phplib_id' in 'field list' ERROR: introducing the new user '192.168.10.182' to the database failed Any idea what's going on? thanks

1 0

[OpenSER-Users] regarding openser v 1.2.0 installation
by Naveen Kumar 08 Jul '08

08 Jul '08

Hi all, i deleted openser.pid from /var/runand then i started [root@info sbin]# openserctl start database engine 'MYSQL' loaded Control engine 'FIFO' loaded Starting OpenSER : ERROR: PID file /var/run/openser.pid does not exist -- OpenSER start failed and then i started like: [root@info sbin]# openser start 0(22725) cfg. warning: (28,15-16): tls support not compiled in 0(22725) cfg. warning: (29,10-13): tls support not compiled in 0(22725) cfg. warning: (30,21-22): tls support not compiled in 0(22725) cfg. warning: (31,21-22): tls support not compiled in 0(22725) cfg. warning: (32,34-35): tls support not compiled in 0(22725) cfg. warning: (33,14-19): tls support not compiled in 0(22725) cfg. warning: (34,20-21): tls support not compiled in 0(22725) cfg. warning: (35,20-21): tls support not compiled in 0(22725) cfg. warning: (36,16-17): tls support not compiled in 0(22725) loading module /usr/local/lib/openser/modules/mysql.so 0(22725) loading module /usr/local/lib/openser/modules/sl.so 0(22725) loading module /usr/local/lib/openser/modules/tm.so 0(22725) DEBUG: register_pv: tm 0(22725) xl_add_extra_spec: extra items list is not initialized 0(22725) xl_add_extra_spec: inserting extra item [T_branch_idx] at [0] 0(22725) xl_add_extra_spec: inserting extra item [T_reply_code] at [1] 0(22725) loading module /usr/local/lib/openser/modules/rr.so 0(22725) loading module /usr/local/lib/openser/modules/maxfwd.so 0(22725) loading module /usr/local/lib/openser/modules/usrloc.so 0(22725) loading module /usr/local/lib/openser/modules/registrar.so 0(22725) loading module /usr/local/lib/openser/modules/textops.so 0(22725) loading module /usr/local/lib/openser/modules/mi_fifo.so 0(22725) loading module /usr/local/lib/openser/modules/auth.so 0(22725) loading module /usr/local/lib/openser/modules/auth_db.so 0(22725) set_mod_param_regex: mi_fifo matches module mi_fifo 0(22725) set_mod_param_regex: found <fifo_name> in module mi_fifo [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: usrloc matches module usrloc 0(22725) set_mod_param_regex: found <db_mode> in module usrloc [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: usrloc matches module usrloc 0(22725) set_mod_param_regex: found <db_url> in module usrloc [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: auth_db matches module auth_db 0(22725) set_mod_param_regex: found <db_url> in module auth_db [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: auth_db matches module auth_db 0(22725) set_mod_param_regex: found <calculate_ha1> in module auth_db [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: auth_db matches module auth_db 0(22725) set_mod_param_regex: found <password_column> in module auth_db [/usr/local/lib/openser/modules/] 0(22725) set_mod_param_regex: rr matches module rr 0(22725) set_mod_param_regex: found <enable_full_lr> in module rr [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <mf_process_maxfwd_header>(1) in module maxfwd [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <record_route>(0) in module rr [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <loose_route>(0) in module rr [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <append_hf>(1) in module textops [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <append_hf>(1) in module textops [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <www_authorize>(2) in module auth_db [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <www_challenge>(2) in module auth [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <save>(1) in module registrar [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <lookup>(1) in module registrar [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <append_hf>(1) in module textops [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <lookup>(1) in module registrar [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <sl_send_reply>(2) in module sl [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <append_hf>(1) in module textops [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <t_relay>(0) in module tm [/usr/local/lib/openser/modules/] 0(22725) find_cmd_export_t: found <sl_reply_error>(0) in module sl [/usr/local/lib/openser/modules/] ERROR: bad config file (9 errors) 0(22725) INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid was not allocated -> nothing to destroy 0(22725) DEBUG: tm_shutdown : start 0(22725) DEBUG: tm_shutdown : emptying hash table 0(22725) DEBUG: tm_shutdown : releasing timers 0(22725) DEBUG: tm_shutdown : removing semaphores 0(22725) DEBUG: tm_shutdown : destroying tmcb lists 0(22725) DEBUG: tm_shutdown : done 0(22725) shm_mem_destroy please anybody help me. With Best Regards, Naveen.

5 7

[OpenSER-Users] ERROR: load_module: could not open module
by suresh tattikota 08 Jul '08

08 Jul '08

hi all i am getting these errors wile running the openser *ERROR: load_module: could not open module </usr/src/OpenSER/openser-1.2.0-* ** *tls/modules/pna.so>: /usr/src/OpenSER/openser-1.2.0-tls/modules/pna.so: cannot open shared object file: No such file or directory * *openser: parse error (54,13-14): failed to load module* *ERROR: no version info in module </usr/local/lib/openser/modules/pna.so>: /usr/local/lib/openser/modules/pna.so: undefined symbol: module_version* * ERROR: no version info in module </usr/local/lib/openser/modules/pna.so>: /usr/local/lib/openser/modules/pna.so: undefined symbol: module_version * thank u

2 1

← Newer
1
...
13
14
15
16
17
18
19
20
21
Older →

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 July 2008