sr-users July 2007

sr-users@lists.kamailio.org

163 participants
262 discussions

[OpenSER-Users] Re: [Serusers] enum_query from failure route
by Jiri Kuthan 12 Jul '07

12 Jul '07

At 12:08 12/07/2007, JF wrote: >So, if I want to perform some less simple (e.g. enum_query) processing >on failed requests, I should loop the request through SER again and do >it in request route? > >Not a very nice way to solve it. Well sometimes a big-hammer approach features design simplicity which is good (simple to understand, audit, maintain, ....) and can be used to solve problems on serial basis. I personally find this quite a good solution. > One more Record-Route, bigger >message... parsing the whole thing again. parsing yes, you don't have to record-route each pass. -jiri >Andrei, what exactly is the problem regarding long processing in >failure route, and what could be done to fix it? > >Thanks, >JF > >On 7/11/07, Jiri Kuthan <jiri(a)iptel.org> wrote: >>At 21:22 11/07/2007, Martin Hoffmann wrote: >>>Jiri Kuthan wrote: >>>> At 16:41 11/07/2007, JF wrote: >>>> > >>>> >Is there any particular reason why enum_query cannot be called from >>>> >FAILURE_ROUTE? >>>> >>>> Not sure. I think it is possible to turn it on but possibly ENUM's processing >>>> latency may conflict with the failure_route located in the middle of >>>> transaction >>>> processing and lead to some blocknig conditions, current TM >>>> maintainer, Andrei, will >>>> certainly know better. >>> >>>In short: There may be dragons there. >>> >>>Anyways, I am not sure what you want to do, but you can usually skip the >>>problem by fixing the Request-URI and sprialing the call to yourself. >>> >>>For instance, if call forwarding is what you're after, instead of >>>re-setting the target and just running processing again, you can just >>>stuff the URI you want to forward to in the Request-URI and call >>>t_relay() (don't forget the append_branch() if in a failure_route). >>> >>>As a rule, keep failure and onreply routes simple. Actually, as a rule, >>>keep your config simple (Though simple does not necessarly mean short). >> >>Indeed: KISS applies to ser.cfg very well. >> >>-jiri >> >> >> >> >>-- >>Jiri Kuthan http://iptel.org/~jiri/ >> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers > > > >-- >Jiri Kuthan http://iptel.org/~jiri/

1 0

[OpenSER-Users] Question on force-active parameter of presence-xml module
by Michel de Boer 12 Jul '07

12 Jul '07

Hi, According to the documentation if the force-active parameter is set to 0, openser will consult the xcap_table when a SUBCRIBE for presence comes in. If there is no entry in the xcap_table, the watcher will receive NOTIFY messages with an empty body until the presentity authorizes the watcher. However, in my tests it doesn't seem to matter to what value I set force_active. The watcher always gets the presence state of the presentity. For my current tests this is fine as I don't have support for xcap, but it looks wrong to me. Can someone explain me how the force-active parameter works? I am using the devel version of openser. Regards, Michel -- Michel de Boer www.twinklephone.com

1 0

Re: [OpenSER-Users] BLA errors
by Jeremy George 12 Jul '07

12 Jul '07

Hi Anca, Thanks for the quick reply. I wondered a little about the phones, too. Alan sent me a note privately, very tactfully reminding me that I'd sent less phone information than I should have. The Polycom 650: bootrom.ld version: 3.2.3.0002 sip version: 2.1.2.0078 The Polycom 330: bootrom.lod verion: 3.2.3.0021 sip version: 2.1.2.0049 Both phone.cfgs are attached, as well ngrep traces from reboots. I did two traces, rebooting each phone separately. Again, I appreciate the help very much. Thanks. - Jeremy >-----Original Message----- >From: Anca-Maria Vamanu [mailto:anca@voice-system.ro] >Sent: Thursday, July 12, 2007 08:18 AM >To: 'Jeremy George' >Cc: users(a)openser.org >Subject: Re: [OpenSER-Users] BLA errors > >Hello, > >The implementation of the bla extension has been done according to the >specifications in draft-anil-sipping-bla-03.txt, and tested with >Polycom 430. > Since we received positive feedback from users impementing BLA, I am >thinking that the phones you use have a different behaviour and that >here is the cause of the errors. >To detect the exact cause I would need some more data. Could you send >me a part of the log , after starting openser and the first phones >registers, subscribes and is sent a Notify? > >regards, > >Anca Vamanu > >Jeremy George wrote: > >>Hello All, >> >> I have BLA implemented, with errors. An ngrep trace of relevant packets >>showing errors follows. The configurations of both main proxy and bla >>presence server are attached. >> >> I stripped the main proxy to the bone. No outside routing at all. The >>bla presence server is almost all from the sample. >> >> 75.56.10.115 is a Cisco 7960 with one line registered: jeremy/private >> 75.56.10.116 is a Polycom 650 with two lines registered: jessica/private >> and helen/shared >> 75.56.10.117 is a Polycom 330 with two lines registered: didama/private >> and helen/shared >> 128.91.3.19 is the main proxy running openser v1.2.1 . >> 128.91.2.215 is the bla presence server running openser svn 2413 . >> >> This error: "1(1184) PUA:subs_cback_func: no reply message found" is >>being produced repeatedly on the bla presence server. >> >> Finally, I'm getting these error messages on the bla presence server: >> >> 0(1284) PUA_BLA: handle_notify: ERROR Notify in a non existing dialog >> 0(1284) WARNING: script writer didn't release transaction >> >> From time-to-time pua entries eat all of available memory. Curiously, >>they were all for the Polycom 330 and none were for the Polycom 650. >> >> Any help is greatly appreciated. Thanks. >> >>- Jeremy >> >> >> > >

2 2

[Serusers] Meaning of and proper response for a 401
by SIP 12 Jul '07

12 Jul '07

There's a UA in our network that responds to a reinvite with a 401. U PROXY.IP.ADDRESS:5060 -> UA.IP.ADDRESS:63718 INVITE sip:1101XXXXXXX@UA.IP.ADDRESS:63718 SIP/2.0. Record-Route: <sip:PROXY.IP.ADDRESS;ftag=as7bbe322e;lr=on>. Via: SIP/2.0/UDP PROXY.IP.ADDRESS;branch=z9hG4bK9159.cd2a95b4.0. Via: SIP/2.0/UDP PSTN.GW.IP:5090;branch=z9hG4bK39c17f01;rport=5090. From: <sip:13154476314@our.domain.com>;tag=as7bbe322e. To: "User One" <sip:1101XXXXXXX@our.domain.com>;tag=202d9942. Contact: <sip:13154476314@PSTN.GW.IP:5090>. Call-ID: 6b3f44351f5fab945ac212a2141df93a(a)UA.IP.ADDRESS. CSeq: 102 INVITE. User-Agent: Asterisk PBX. Max-Forwards: 16. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 314. P-hint: LR. . v=0. o=root 15241 15243 IN IP4 216.143.130.90. s=session. c=IN IP4 216.143.130.90. t=0 0. m=audio 17192 RTP/AVP 0 8 18 3 101. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:3 GSM/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=silenceSupp:off - - - -. # U UA.IP.ADDRESS:63718 -> PROXY.IP.ADDRESS:5060 SIP/2.0 410 Gone. Via: SIP/2.0/UDP PROXY.IP.ADDRESS:5060;branch=z9hG4bK9159.cd2a95b4.0. Via: SIP/2.0/UDP PSTN.GW.IP:5090;branch=z9hG4bK39c17f01;rport=5090. From: <sip:13154476314@our.domain.com>;tag=as7bbe322e. To: "User One" <sip:1101XXXXXXX@our.domain.com>;tag=202d9942. Contact: <sip:1101XXXXXXX@UA.IP.ADDRESS:63718>. Call-ID: 6b3f44351f5fab945ac212a2141df93a(a)UA.IP.ADDRESS. CSeq: 102 INVITE. Content-Length: 0. First off, I thought a 410 was supposed to be unauthorised (what is 'Gone' ?). Secondly... is the UA requesting our server to authorise its reinvite, or is something else going on here I clearly don't follow? N.

2 2

[OpenSER-Users] query: how to deal with crazy clients
by Klaus Darilion 12 Jul '07

12 Jul '07

Hi! I once again bother about a stupid SIP client which is misconfigured and sending REGISTER messages like crazy to my SIP proxy (~20 requests/second). How do you deal with that stupid clients. Manual blocking does not work as the client has dynamic IP addresses. I once also tried the pike module but had problems to find out a proper configuration (threshold value and sampling interval). Further, I think blocking at IP level (e.g. openser injects iptable rules) would be more useful. I would be happy to hear how you handle such situations.

2 3

[OpenSER-Users] SER query regarding mysql
by Parminder.Nayyar＠relianceada.com 12 Jul '07

12 Jul '07

hi, we are facing following problem while using SER with mysql data base. The problem statements are as follows: 0(0) find_mod_export: found <db_update> in module mysql [/export/home/mins/SER/lib/ser/modules/mysql.so] 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/maxfwd.so mf_process_maxfwd_header 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/rr.so record_route 0(0) fixing /export/home/mins/SER/lib/ser/modules/rr.so loose_route 0(0) fixing /export/home/mins/SER/lib/ser/modules/tm.so t_relay 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/tm.so t_relay 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_reply_error 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth_db.so www_authorize 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so www_challenge 0(0) fixing /export/home/mins/SER/lib/ser/modules/uri_db.so check_to 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so consume_credentials 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so save 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_reply_error 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth_db.so proxy_authorize 0(0) get_connection(): Connection not found in the pool 0(0) release_connection(): Removing connection from the pool 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so proxy_challenge 0(0) fixing /export/home/mins/SER/lib/ser/modules/auth.so consume_credentials 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/registrar.so lookup 0(0) fixing /export/home/mins/SER/lib/ser/modules/sl.so sl_send_reply 0(0) INFO: udp_init: SO_RCVBUF is initially 65536 0(0) DEBUG: udp_init: trying SO_RCVBUF: 131072 0(0) DEBUG: setting SO_RCVBUF; set=131072,verify=131072 0(0) DEBUG: udp_init: trying SO_RCVBUF: 262144 0(0) DEBUG: setting SO_RCVBUF; set=262144,verify=262144 0(0) INFO: udp_init: SO_RCVBUF is finally 262144 0(0) ERROR: tcp_init: bind(5, e83bc, 16) on 10.128.16.254: Address already in use 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(20185) shm_mem_destroy 0(20185) destroying the shared memory lock The ser.cfg file used is attached with the mail. Plz sugest me some solution for mentioned problem... thanx 'n' regds, Parminder Nayyar

3 2

[OpenSER-Users] BLA errors
by Jeremy George 12 Jul '07

12 Jul '07

Hello All, I have BLA implemented, with errors. An ngrep trace of relevant packets showing errors follows. The configurations of both main proxy and bla presence server are attached. I stripped the main proxy to the bone. No outside routing at all. The bla presence server is almost all from the sample. 75.56.10.115 is a Cisco 7960 with one line registered: jeremy/private 75.56.10.116 is a Polycom 650 with two lines registered: jessica/private and helen/shared 75.56.10.117 is a Polycom 330 with two lines registered: didama/private and helen/shared 128.91.3.19 is the main proxy running openser v1.2.1 . 128.91.2.215 is the bla presence server running openser svn 2413 . This error: "1(1184) PUA:subs_cback_func: no reply message found" is being produced repeatedly on the bla presence server. Finally, I'm getting these error messages on the bla presence server: 0(1284) PUA_BLA: handle_notify: ERROR Notify in a non existing dialog 0(1284) WARNING: script writer didn't release transaction From time-to-time pua entries eat all of available memory. Curiously, they were all for the Polycom 330 and none were for the Polycom 650. Any help is greatly appreciated. Thanks. - Jeremy # U 128.91.2.215:5060 -> 75.56.10.117:5060 SUBSCRIBE sip:helen@75.56.10.117 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;bra nch=z9hG4bKd187.ae440494.0..To: sip:helen@75.56.10.117;tag=9D362AB1-962A397 2..From: sip:helen@128.91.2.215;tag=45cdb744f974e73ed68392c080e87bb4-2684.. CSeq: 11 SUBSCRIBE..Call-ID: 7df1b9fa-810@128.91.2.215..Content-Length: 0.. User-Agent: OpenSER (1.3.0-dev7-tls (i386/linux))..Event: dialog;sla..Conta ct: <sip:helen@128.91.2.215>..Expires: 1810.... # U 75.56.10.117:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bKd187.9e440494.0..From: <sip:helen@128.91.2.215>;tag=45cdb 744f974e73ed68392c080e87bb4-2684..To: <sip:helen@75.56.10.117>;tag=9D362AB1 -962A3972..CSeq: 11 SUBSCRIBE..Call-ID: 7df1b9fa-810@128.91.2.215..Event: d ialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Content- Length: 0.... # # U 128.91.2.215:5060 -> 75.56.10.117:5060 SUBSCRIBE sip:helen@75.56.10.117 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;bra nch=z9hG4bK0de3.730cc385.0..To: sip:helen@75.56.10.117..From: sip:helen@128 .91.2.215;tag=45cdb744f974e73ed68392c080e87bb4-be09..CSeq: 10 SUBSCRIBE..Ca ll-ID: 7df1ba94-810@128.91.2.215..Content-Length: 0..User-Agent: OpenSER (1 .3.0-dev7-tls (i386/linux))..Event: dialog;sla..Contact: <sip:helen@128.91. 2.215>..Expires: 1820.... # U 75.56.10.117:5060 -> 128.91.2.215:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 128.91.2.215;branch=z9hG4bK0de3.730cc385.0 ..From: <sip:helen@128.91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09. .To: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD3A4..CSeq: 10 SUBSCRIBE..Ca ll-ID: 7df1ba94-810@128.91.2.215..Contact: <sip:helen@75.56.10.117>..Event: dialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Expire s: 1820..Content-Length: 0.... # # U 128.91.3.19:5060 -> 75.56.10.116:5060 SUBSCRIBE sip:helen@75.56.10.116 SIP/2.0..Record-Route: <sip:128.91.3.19;lr =on;ftag=36887A42-5425822F>..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d 4.3e70f5b4.2..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E. .From: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:hele n@128.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: aa7d279b-1806c1f8-b6acbe85 @75.56.10.117..Contact: <sip:helen@75.56.10.117>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..Ev ent: call-info..User-Agent: PolycomSoundPointIP-SPIP_330-UA/2.1.2.0049..Max -Forwards: 70..Expires: 1800..Content-Length: 0.... # U 75.56.10.117:5060 -> 128.91.3.19:5060 SIP/2.0 482 Loop Detected..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d4. 3e70f5b4.0..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E..F rom: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:helen@ 128.91.3.19:5060>..CSeq: 1 SUBSCRIBE..Call-ID: aa7d279b-1806c1f8-b6acbe85@7 5.56.10.117..Contact: <sip:helen@75.56.10.117>..Record-Route: <sip:128.91.3 .19;lr=on;ftag=36887A42-5425822F>..Event: call-info..User-Agent: PolycomSou ndPointIP-SPIP_330-UA/2.1.2.0049..Content-Length: 0.... # U 75.56.10.116:5060 -> 128.91.3.19:5060 SIP/2.0 501 Not Implemented..Via: SIP/2.0/UDP 128.91.3.19;branch=z9hG4bK27d 4.3e70f5b4.1..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bKa5b69571873BC26E. .From: "Helen" <sip:helen@128.91.3.19>;tag=36887A42-5425822F..To: <sip:hele n@128.91.3.19:5060>;tag=BC1615E5-7F8E8B8C..CSeq: 1 SUBSCRIBE..Call-ID: aa7d 279b-1806c1f8-b6acbe85@75.56.10.117..Contact: <sip:helen@75.56.10.116>..Rec ord-Route: <sip:128.91.3.19;lr=on;ftag=36887A42-5425822F>..Event: call-info ..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Expires: 1800..Co ntent-Length: 0.... # # U 75.56.10.117:5060 -> 128.91.2.215:5060 NOTIFY sip:helen@128.91.2.215 SIP/2.0..Via: SIP/2.0/UDP 75.56.10.117;branch =z9hG4bK70de934cAD6A9A99..From: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD 3A4..To: <sip:helen@128.91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09 ..CSeq: 1 NOTIFY..Call-ID: 7df1ba94-810@128.91.2.215..Contact: <sip:helen@7 5.56.10.117>..Event: dialog;sla..User-Agent: PolycomSoundPointIP-SPIP_330-U A/2.1.2.0049..Subscription-State: active;expires=1818..Max-Forwards: 70..Co ntent-Type: application/dialog-info+xml..Content-Length: 156....<?xml versi on="1.0"?>..<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version ="0" state="full" entity="sip:helen@128.91.3.19:5060">..</dialog-info> # U 128.91.2.215:5060 -> 75.56.10.117:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 75.56.10.117;branch=z9hG4bK70de934cAD6A9A9 9..From: <sip:helen@75.56.10.117>;tag=8C7BE007-7BDCD3A4..To: <sip:helen@128 .91.2.215>;tag=45cdb744f974e73ed68392c080e87bb4-be09..CSeq: 1 NOTIFY..Call- ID: 7df1ba94-810@128.91.2.215..Server: OpenSER (1.3.0-dev7-tls (i386/linux) )..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bK8d7b.ab428dd3.0..To: sip:helen@128.91.3.19;tag=FBC67234-A17D6FE3..F rom: sip:helen@128.91.2.215;tag=10.810.1184176700.14..CSeq: 3 NOTIFY..Call- ID: a023d5f7-3f2d49fe-76f2717d@75.56.10.116..Content-Length: 156..User-Agen t: OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;s la..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=32 83..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dia log-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="ful l" entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bK8d7b.ab428dd3.0..From: <sip:helen@128.91.2.215>;tag=10.81 0.1184176700.14..To: <sip:helen@128.91.3.19>;tag=FBC67234-A17D6FE3..CSeq: 3 NOTIFY..Call-ID: a023d5f7-3f2d49fe-76f2717d@75.56.10.116..Event: dialog;sl a..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bK06ea.193b0e22.0..To: sip:helen@128.91.3.19;tag=D976CBBC-2176183F..F rom: sip:helen@128.91.2.215;tag=10.810.1184176890.21..CSeq: 2 NOTIFY..Call- ID: e11fdddb-9530f65a-3123a455@75.56.10.116..Content-Length: 156..User-Agen t: OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;s la..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=34 73..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dia log-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="ful l" entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 481 Call Leg/Transaction Does Not Exist..Via: SIP/2.0/UDP 128.91.2. 215;branch=z9hG4bK06ea.193b0e22.0..From: <sip:helen@128.91.2.215>;tag=10.81 0.1184176890.21..To: <sip:helen@128.91.3.19>;tag=D976CBBC-2176183F..CSeq: 2 NOTIFY..Call-ID: e11fdddb-9530f65a-3123a455@75.56.10.116..Event: dialog;sl a..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0.... # U 128.91.2.215:5060 -> 75.56.10.116:5060 NOTIFY sip:helen@75.56.10.116 SIP/2.0..Via: SIP/2.0/UDP 128.91.2.215;branch =z9hG4bKdcf1.0c60f511.0..To: sip:helen@128.91.3.19;tag=18F7DEB-D3FFDEAA..Fr om: sip:helen@128.91.2.215;tag=10.810.1184176985.23..CSeq: 2 NOTIFY..Call-I D: a7685c76-af0100e1-7b4a7078@75.56.10.116..Content-Length: 156..User-Agent : OpenSER (1.3.0-dev7-tls (i386/linux))..Max-Forwards: 70..Event: dialog;sl a..Contact: <sip:128.91.2.215:5060>..Subscription-State: active;expires=356 8..Content-Type: application/dialog-info+xml....<?xml version="1.0"?>.<dial og-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="15" state="full " entity="sip:helen@128.91.3.19:5060">.</dialog-info>. # U 75.56.10.116:5060 -> 128.91.2.215:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 128.91.2.215;branch=z9hG4bKdcf1.0c60f511.0 ..From: <sip:helen@128.91.2.215>;tag=10.810.1184176985.23..To: <sip:helen@1 28.91.3.19>;tag=18F7DEB-D3FFDEAA..CSeq: 2 NOTIFY..Call-ID: a7685c76-af0100e 1-7b4a7078@75.56.10.116..Contact: <sip:helen@75.56.10.116>..Event: dialog;s la..User-Agent: PolycomSoundPointIP-SPIP_650-UA/2.1.2.0078..Content-Length: 0....

2 1

[OpenSER-Users] OT: Asterisk mailing lists down
by Klaus Darilion 12 Jul '07

12 Jul '07

Hi! Am I the only one having problems with the Asterisk lists? thanks klaus

1 0

[Serusers] Help needed
by Azeem Mehmood 12 Jul '07

12 Jul '07

Dear Sir/Madam How are you? I hope you are fine. Can anybody help me installing SER from scratch. With Best Regards Azeem Mehmood ( President) Oskar-Tahir Sp z o.o ul. Regatowa 3A 03-639 Warsaw Poland Phone : +48604826332 WebSite:- www.voip-prof.com Email: voip-prof(a)voip-prof.com

1 0

[OpenSER-Users] OpenSER training course for admins
by Bogdan-Andrei Iancu 12 Jul '07

12 Jul '07

Hi, We have a good opportunity of organizing a one-day training course for OpenSER, specially for people looking for how to configure OpenSER. So, the targeted people are the OpenSER administrators that are looking to learn, via interactive sessions, based on script examples, how to configure different OpenSER features or services. We will try to mainly focus on the most complex and requested configuration cases, like: NAT traversal covering all cases Accounting - basic, extra accounting, multi-leg accounting General frame for routing (sequential request routing) Security (authentication, GW protection, blacklists) Integration to Asterisk (media services) Interdomain peering HA support (replication, GW redundancy) Now,about the course - as I said, it will be one day course and it will be hosted by the VoN Italy in Milan, on 26 September, from 9:30 to 18:00 hours. The package includes breakfast and lunch at the training location and the cost is estimated to be not more than 400 Euro per person. The event is organized in collaboration with Pulvermedia and right now we are looking to see how many people would be interested in this offer (technical side from openser.org and organization from Pulvermedia). Please feel free to contact me for any details/question. As I said, the first step is to see how many people are looking for such event, so let me know if you are interested in it. This survey will be ending Sunday 8th 24:00 CET. All this information will be posted on the openser project web page and forum. So, please give us the feedback regarding this opportunity to see if we go for it or not (also any suggestions are welcomed). Regards, Bogdan

8 10

← Newer
1
...
13
14
15
16
17
18
19
...
27
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 2007