sr-users March 2006

sr-users@lists.kamailio.org

223 participants
505 discussions

by Luis Silva

I there! I'm a novice user using ser and I trying to understand the new dialog module. First of all, is there any documentation about this module? If there isn't, can you tell me what is the objective of using the "bind_dlg_mod" function? Tks in advance

18 years, 8 months

Re: [Serusers] Carrier-grade framework for SER

by Nick Hoffman

On Fri January 21 2005 21:21, "Juha Heinanen" <jh(a)lohi.tutpro.com> wrote: > greger, > > we have done some work on xmlprc based provisioning and it looks > promising. xmlrpc spec is three pages long and even i can understand > it. soap spec, on the other hand, is far too thick and goes way above > my head. > > -- juha On Tue January 25 2005 11:36, "Andreas Granig" <andreas.granig(a)inode.info> wrote: > In short, I plan to write an xmlrpc-based provisioning system for > distributing FIFO commands. The main focus is sharing registration > contacts and aliases among different SERs (all the data that can't be > replicated on a lower (database) layer due to memory caching). > > There's an external application on each SER host receiving contacts from > a SER module via a local socket. These contacts are wrapped into xmlrpc > (in fact the contact is converted into a FIFO command which is wrapped > into xmlrpc) and are distributed to the same application on other SER > hosts, which writes them into the SER FIFO. If an application is > unreachable or reports an error, the distributed FIFO command is queued. > > The application can receive arbitrary FIFO commands, and a flag > indicates if the command should be redistributed to the other hosts. > > Andy Hi guys. Browsing through the archives, I happened upon the "Carrier-grade framework for SER" thread, part of which discusses provisioning SER using XML-RPC. Has anything been released for this at any level of "buggyness" or stability? I'm looking to do provisioning in SER with XML-RPC and would prefer not to have to reinvent the wheel if others have already started/finished it. Thanks for any input! -- Nick e: nick.hoffman(a)altcall.com p: +61 7 5591 3588 f: +61 7 5591 6588 If you receive this email by mistake, please notify us and do not make any use of the email. We do not waive any privilege, confidentiality or copyright associated with it.

18 years, 8 months

[Serusers] I beg you please help me: Radius messages

by Gokhan Uslu

Hi everybody, I really need your help. Please someone help me. I have to modify the values in the parameters of radius authentication messages. The message below is my default message rad_recv: Access-Request packet from host 127.0.0.1:32797, id=191, length=206 User-Name = "33333(a)192.168.10.233" Digest-Attributes = 0x0a073333333333 Digest-Attributes = 0x01103139322e3136382e31302e323333 Digest-Attributes = 0x022a3433666663333939393362393134376561643630366537353961646535366534666536 6534303732 Digest-Attributes = 0x04147369703a3139322e3136382e31302e323333 Digest-Attributes = 0x030a5245474953544552 Digest-Response = "de5d4886be3f94e241b92b5bf160857a" Service-Type = Sip-Session Sip-Uri-User = "33333" NAS-Port = 5060 NAS-IP-Address = 127.0.0.1 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_digest: Converting Digest-Attributes to something sane... Digest-User-Name = "33333" Digest-Realm = "192.168.10.233" Digest-Nonce = "43ffc39993b9147ead606e759ade56e4fe6e4072" Digest-URI = "sip:192.168.10.233" Digest-Method = "REGISTER" rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 0 rlm_realm: Looking up realm "192.168.10.233" for User-Name = "33333(a)192.168.10.233" rlm_realm: No such realm "192.168.10.233" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 users: Matched entry DEFAULT at line 182 modcall[authorize]: module "files" returns ok for request 0 modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type DIGEST In here I want to modfy the User-Name`s value. It is now "33333(a)192.168.10.233" but I want to change it. Also I must change the Digest-URI = "sip:192.168.10.233" parameter`s value. Please help me about radius message modifications. Is it possible with avp_module, but how? Please help me please. I beg all you. Thank you Gokhan USLU

18 years, 8 months

[Serusers] PROBLEM WHIT MYSQL MODULE.HELP ME!!

by Vincenzo Golia D'Augè

Hi all, i'm trying to install SER for the first time for a job at university. I'm using the distribution Fedora Core 2 and I have found some problems. This problems come out when I load the modules for MySQL support:mysql.so,auth.so,auth_db.so Asper having loaded this modules when i try to start SER whith the command serctl start it appears the following error: Starting SER : PID file /var/run/ser.pid does not exist -- SER start failed Checking the file log /va/log/messages I have found out that the errors that I had found trying to start the program were the following: Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: Maxfwd module- initializing Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: new_connection(): Client does not support authentication protocol requested by server; consider upgrading MySQL client Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: db_init(): Could not create a connection Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: ERROR: auth_db_ver: unable to open database connection Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: auth_db:str_fixup(): Error while querying table version Mar 7 15:51:29 localhost /usr/local/sbin/ser[4288]: ERROR: fix_expr : fix_actions error May any of you help me,please?It is quite urgent. Thank you. Hear from you soon. Vincenzo

18 years, 8 months

[Users] Registration Weirdness

by Douglas Garstang

I have a series of Polycom phones that are tying to register with OpenSER. The phone sends a REGISTER message, and OpenSER replies with Unauthorised (all normal). The phone re-sends the REGISTER with the credentials, and OpenSER sends Ok. Here's where it goes downhill. The polycom's appearance display does not change from an unregistered to a registered state, ie it does not change from an empty phone to a filled in one. It doesn't think it's registered eventhought it's gotten an OK. Then, a regular intervals it keeps trying to register again, because it still thinks it wasn't successful. I have some other Polycom phones that are not doing this. All have the same SIP software version, and all essentially have the same xml config files, with minor variations. Happening with OpenSER 1.0.0 and 1.0.1 I have pasted ngrep output of one of these below. Anyone got any ideas? # U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" <sip:2944029@ipt.oneeighty.com>;tag=2A2425B5-B64A4132. To: <sip:2944029@ipt.oneeighty.com>. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c(a)216.187.128.72. Contact: <sip:2944029@216.187.128.72>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Max-Forwards: 70. Expires: 3600. Content-Length: 0. . # U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKca28b8d3BC755D46. From: "Sandy Sauvageau" <sip:2944029@ipt.oneeighty.com>;tag=2A2425B5-B64A4132. To: <sip:2944029@ipt.oneeighty.com>;tag=136c3bb27674cf7e44f7b05275ffaecc.0629. CSeq: 1 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c(a)216.187.128.72. WWW-Authenticate: Digest realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d". Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. . # U 216.187.128.72:5060 -> 216.187.140.233:5060 REGISTER sip:ipt.oneeighty.com SIP/2.0. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" <sip:2944029@ipt.oneeighty.com>;tag=2A2425B5-B64A4132. To: <sip:2944029@ipt.oneeighty.com>. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c(a)216.187.128.72. Contact: <sip:2944029@216.187.128.72>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER". User-Agent: PolycomSoundPointIP-SPIP_601-UA/1.6.3.0067. Authorization: Digest username="2944029", realm="ipt.oneeighty.com", nonce="440e4b3f113243b90ba483b6a2f243ea51377e2d", uri="sip:ipt.oneeighty.com", response="9d8b4708296f3fb88d5cfd453121860d", algorithm=MD5. Max-Forwards: 70. Expires: 3600. Content-Length: 0. . # U 216.187.140.233:5060 -> 216.187.128.72:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP 216.187.128.72;branch=z9hG4bKff7cb008AF06A32B. From: "Sandy Sauvageau" <sip:2944029@ipt.oneeighty.com>;tag=2A2425B5-B64A4132. To: <sip:2944029@ipt.oneeighty.com>;tag=136c3bb27674cf7e44f7b05275ffaecc.32b4. CSeq: 2 REGISTER. Call-ID: 56150889-214b0f7f-e02e6d9c(a)216.187.128.72. Contact: <sip:2944029@216.187.128.72>;expires=3600. Server: OpenSer (1.0.0 (i386/linux)). Content-Length: 0. .

18 years, 8 months

[Serusers]How to add TLS support on SER?

by Ren-Huang Liou

Hi, I found nothing about TLS support in serdev.pdf and seruser.pdf. However, I discover the following information : http://lists.iptel.org/pipermail/serdev/2005-March/004037.html Could anyone tell me how to configure TLS on SER 0.96 ? Any documentation? Thanks in advance Best regards, Ren-Huang Liou

18 years, 8 months

[Users] Change default users and password in MySQL problems

by david.castro

Hello. I'm David. I'm working with openser 1.0.1 and MySQL 5.0.18. I'd like changing defaults users and passwords to openser talk to MySQL. I edited "openser_mysql.sh" and I changed some variables in that file. I execute "openser_mysql.sh" and the database was created fine. I wrote next statment in openser.cfg: modparam("auth_db", "db_url", "mysql://user:pass@localhost/openser"). Indeed user and pass are the same in mysql. I run openser but gives an error: 0(0) new_connection: Access denied for user 'openser'@'localhost' (using password: YES) I don't have any user called openser in MySQL because I changed "openser_mysql.sh". How I change the defaults users and passwords in openser? Thank you. -- ------------------------------- David Castro Mosquera Adianta Tel: (34) 902 999 178 Fax: (34) 902 501 437 Email: david.castro(a)adianta.net Web: www.adianta.net -------------------------------

18 years, 8 months

[Serusers] Installing SER using SUSE 10

by Dennis Yongco

Hello serusers! Need help. I tried to install SER 0.9.6 using SUSE 10 and I encountered RPM build errors using ser.spec.SuSE inside rpm directory. I installed all requirements as stated in INSTALL file and radiusclient-ng before installing SER. TIA. Listed below are last portions of the rpmbuild: Requires: /bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.3) libc.so.6(GLIBC_2.3.4) libdl.so.2 libdl.so.2(GLIBC_2.0) libdl.so.2(GLIBC_2.1) libresolv.so.2 libresolv.so.2(GLIBC_2.2) Conflicts: ser < 0.9.6 ser-mysql < 0.9.6 ser-jabber < 0.9.6 ser-radius < 0.9.6 Processing files: ser-mysql-0.9.6-0.suse910 Finding Provides: /usr/lib/rpm/find-provides Finding Requires: /usr/lib/rpm/find-requires Provides: mysql.so Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: ser = 0.9.6 /bin/sh libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libmysqlclient.so.12 libz.so.1 Processing files: ser-jabber-0.9.6-0.suse910 Finding Provides: /usr/lib/rpm/find-provides Finding Requires: /usr/lib/rpm/find-requires Provides: jabber.so Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: ser = 0.9.6 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.3) libexpat.so.0 Processing files: ser-radius-0.9.6-0.suse910 Finding Provides: /usr/lib/rpm/find-provides Finding Requires: /usr/lib/rpm/find-requires Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: ser = 0.9.6 Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/ser-0.9.6-root error: Installed (but unpackaged) file(s) found: /usr/lib/ser/modules/auth_radius.so /usr/lib/ser/modules/group_radius.so /usr/lib/ser/modules/uri_radius.so RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib/ser/modules/auth_radius.so /usr/lib/ser/modules/group_radius.so /usr/lib/ser/modules/uri_radius.so linux:/usr/src/packages/SPECS # ________________________________________________ Message sent using UebiMiau 2.7.9

18 years, 8 months

[Serusers] serweb error

by Joao Pereira

Hello to all I installed the most recent serweb, but when I try to register a new user, there is always an error like this: Fatal error: Call to undefined function: imap_8bit() in /serweb-0.9.4/html/functions.php on line 312 It says that he doesnt understand the "imap_8bit" function. Did someone had this problem? Thanks Joao Pereira

18 years, 8 months

[Users] OperSER can't handle a maddr tag in the RURI

by Dr. Rodney G. McDuff

I am try to get Windows Messenger v5.1 to play nicely with other UAs and SER/OpenSER and Asterisk. One of the problems that is confounding me is WM5 non-standard contact header which is of the form: Contact: <sip:user@domain.net:5060;maddr=xxx.xxx.152.57;transport=tcp>;proxy=replace. The SIP RFC say that a maddr URL tag overrides the host part of the url (at least for the Via header). However when a UA uses this contact to send an ACK or BYE back to the WM5 UA , OpenSER does seem to be able to route it to xxx.xxx.152.57. If fact Openser pops the route header off (which contains the IP for the proxy) into the RURI and the response goes nowhere. (See attached trace) When I rewrite the contact in the config file but put the following code in route[0]: if (method=="INVITE") { if (search("^Contact:.*;maddr=")) { # find the host name and replace it withj the maddr tag if (!subst("/^Contact:(.*)sip:([^@]+)@([a-zA-Z0-9.]+)(.*);maddr=([0-9.]+)(.*)/Contact:\1sip:\2@\5\4;maddr=\5\6/i")) { xlog("L_NOTICE", "route[0]: ERROR rewriting maddr contact $hdr(contact[0])\n"); } else { xlog("L_NOTICE", "route[0]: Rewrote maddr contact $hdr(contact[0])\n"); } } } and the following in onreply_route[1]: if (status=="200") { if (search("^Contact:.*;maddr=")) { # find the host name and replace it withj the maddr tag if (!subst("/^Contact:(.*)sip:([^@]+)@([a-zA-Z0-9.]+)(.*);maddr=([0-9.]+)(.*)/Contact:\1sip:\2@\5\4;maddr=\5\6/i")) { xlog("L_NOTICE", "onreply_route[1]: ERROR rewriting maddr contact $hdr(contact[0])\n"); } else { xlog("L_NOTICE", "onreply_route[1]: Rewrote maddr contact $hdr(contact[0])\n"); } } } the calls proceed and terminate correctly in both directions. The question then arises should OpenSER handle maddr URL tags in the RURI PS. Does anyone know what the proxy=replace header tag means? -- Dr. Rodney G. McDuff |Ex ignorantia ad sapientiam Manager, Strategic Technologies Group| Ex luce ad tenebras Information Technology Services | The University of Queensland | EMAIL: mcduff(a)its.uq.edu.au | TELEPHONE: +61 7 3365 8220 | # T XXX.XXX.152.78:1399 -> XXX.XXX.2.40:5060 [AP] INVITE sip:userwm5@domain.net SIP/2.0. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-9808374cf435475c-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: <sip:userwm5@domain.net>. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Supported: eventlist. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 619. . v=0. o=- 5401759 5401834 IN IP4 XXX.XXX.152.78. s=CounterPath eyeBeam. c=IN IP4 XXX.XXX.152.78. t=0 0. m=audio 8972 RTP/AVP 8 0 100 6 3 18 98 97 5 102 101. a=alt:1 1 : 09A01121 0000002D XXX.XXX.152.78 8972. a=fmtp:101 0-15. a=rtpmap:100 speex/16000. a=rtpmap:98 ilbc/8000. a=rtpmap:97 speex/8000. a=rtpmap:102 l16/16000. a=rtpmap:101 telephone-event/8000. a=sendrecv. m=video 8974 RTP/AVP 103 105 34 120. a=alt:1 1 : F4D11C0A 000000FA XXX.XXX.152.78 8974. a=fmtp:105 profile=3;level=20. a=fmtp:34 CIF=2 QCIF=2 MAXBR=5120. a=rtpmap:103 h263-1998/90000. a=rtpmap:105 h263-2000/90000. a=rtpmap:120 h263/90000. a=sendrecv. # T XXX.XXX.2.40:5060 -> XXX.XXX.152.78:1399 [AP] SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-9808374cf435475c-1--d87543-;rport=1399. To: <sip:userwm5@domain.net>;tag=88cbe004b15faf54e2a8ed57b9c4eaaa.ce87. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 INVITE. Proxy-Authenticate: Digest realm="domain.net", nonce="440b877a9197230dccf837b9adb629fd8ebf8115". Server: OpenSer (1.0.1-tls (i386/linux)). Content-Length: 0. Warning: 392 XXX.XXX.2.40:5060 "Noisy feedback tells: pid=4962 req_src_ip=XXX.XXX.152.78 req_src_port=1399 in_uri=sip:userwm5@domain.net out_uri=sip:userwm5@domain.net via_cnt==1". . # T XXX.XXX.152.78:1399 -> XXX.XXX.2.40:5060 [AP] ACK sip:userwm5@domain.net SIP/2.0. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-9808374cf435475c-1--d87543-;rport. To: <sip:userwm5@domain.net>;tag=88cbe004b15faf54e2a8ed57b9c4eaaa.ce87. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 ACK. Content-Length: 0. . # T XXX.XXX.152.78:1399 -> XXX.XXX.2.40:5060 [A] INVITE sip:userwm5@domain.net SIP/2.0. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: <sip:userwm5@domain.net>. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Proxy-Authorization: Digest username="usereb",realm="domain.net",nonce="440b877a9197230dccf837b9adb629fd8ebf8115",uri="sip:userwm5@domain.net",response="4b8c1425b2edd0c05302ec708a793316",algorithm=MD5. Supported: eventlist. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 619. . v=0. o=- 5401759 5401834 IN IP4 XXX.XXX.152.78. s=CounterPath eyeBeam. c=IN IP4 XXX.XXX.152.78. t=0 0. m=audio 8972 RTP/AVP 8 0 100 6 3 18 98 97 5 102 101. a=alt:1 1 : 09A01121 0000002D XXX.XXX.152.78 8972. a=fmtp:101 0-15. a=rtpmap:100 speex/16000. a=rtpmap:98 ilbc/8000. a=rtpmap:97 speex/8000. a=rtpmap:102 l16/16000. a=rtpmap:101 telephone-event/8000. a=sendrecv. m=video 8974 RTP/AVP 103 105 34 120. a=alt:1 1 : F4D11C0A 000000FA XXX.XXX.152.78 8974. a=fmt # T XXX.XXX.152.78:1399 -> XXX.XXX.2.40:5060 [AP] p:105 profile=3;level=20. a=fmtp:34 CIF=2 QCIF=2 MAXBR=5120. a=rtpmap:103 h263-1998/90000. a=rtpmap:105 h263-2000/90000. a=rtpmap:120 h263/90000. a=sendrecv. # T XXX.XXX.2.40:5060 -> XXX.XXX.152.78:1399 [AP] SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. To: <sip:userwm5@domain.net>. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Server: OpenSer (1.0.1-tls (i386/linux)). Content-Length: 0. Warning: 392 XXX.XXX.2.40:5060 "Noisy feedback tells: pid=4962 req_src_ip=XXX.XXX.152.78 req_src_port=1399 in_uri=sip:userwm5@domain.net out_uri=sip:YYY.YYY.152.57:5060;transport=tcp via_cnt==1". . # T XXX.XXX.2.40:42734 -> YYY.YYY.152.57:5060 [AP] INVITE sip:YYY.YYY.152.57:5060;transport=tcp SIP/2.0. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp>. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bK95f.22e73805.0;i=535. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. Max-Forwards: 69. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: <sip:userwm5@domain.net>. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Supported: eventlist. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 619. . v=0. o=- 5401759 5401834 IN IP4 XXX.XXX.152.78. s=CounterPath eyeBeam. c=IN IP4 XXX.XXX.2.40. t=0 0. m=audio 35796 RTP/AVP 8 0 100 6 3 18 98 97 5 102 101. a=alt:1 1 : 09A01121 0000002D XXX.XXX.152.78 8972. a=fmtp:101 0-15. a=rtpmap:100 speex/16000. a=rtpmap:98 ilbc/8000. a=rtpmap:97 speex/8000. a=rtpmap:102 l16/16000. a=rtpmap:101 telephone-event/8000. a=sendrecv. m=video 35798 RTP/AVP 103 105 34 120. a=alt:1 1 : F4D11C0A 000000FA XXX.XXX.152.78 8974. a=fmtp:105 profile=3;level=20. a=fmtp:34 CIF=2 QCIF=2 MAXBR=5120. a=rtpmap:103 h263-1998/90000. a=rtpmap:105 h263-2000/90000. a=rtpmap:120 h263/90000. a=sendrecv. # T YYY.YYY.152.57:5060 -> XXX.XXX.2.40:42734 [AP] SIP/2.0 100 Trying. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bK95f.22e73805.0;i=535. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. User-Agent: RTC/1.3. Content-Length: 0. . # T YYY.YYY.152.57:5060 -> XXX.XXX.2.40:42734 [AP] SIP/2.0 180 Ringing. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bK95f.22e73805.0;i=535. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp>. User-Agent: RTC/1.3. Content-Length: 0. . # T XXX.XXX.2.40:5060 -> XXX.XXX.152.78:1399 [AP] SIP/2.0 180 Ringing. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp>. User-Agent: RTC/1.3. Content-Length: 0. . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # T YYY.YYY.152.57:5060 -> XXX.XXX.2.40:42734 [AP] SIP/2.0 200 OK. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bK95f.22e73805.0;i=535. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp>. Contact: <sip:userwm5@domain.net:5060;maddr=YYY.YYY.152.57;transport=tcp>;proxy=replace. User-Agent: RTC/1.3. Content-Type: application/sdp. Content-Length: 390. . v=0. o=- 0 0 IN IP4 YYY.YYY.152.57. s=CounterPath eyeBeam. c=IN IP4 YYY.YYY.152.57. b=CT:1000. t=0 0. m=audio 5350 RTP/AVP 8 0 6 3 5 101. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:6 DVI4/16000. a=rtpmap:3 GSM/8000. a=rtpmap:5 DVI4/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. m=video 5352 RTP/AVP 34 120. a=recvonly. a=rtpmap:34 H263/90000. a=rtpmap:120 h263/90000. # T XXX.XXX.2.40:5060 -> XXX.XXX.152.78:1399 [AP] SIP/2.0 200 OK. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-dd728d06512ec00b-1--d87543-;rport=1399. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 INVITE. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp>. Contact: <sip:userwm5@domain.net:5060;maddr=YYY.YYY.152.57;transport=tcp>;proxy=replace. User-Agent: RTC/1.3. Content-Type: application/sdp. Content-Length: 390. . v=0. o=- 0 0 IN IP4 YYY.YYY.152.57. s=CounterPath eyeBeam. c=IN IP4 XXX.XXX.2.40. b=CT:1000. t=0 0. m=audio 35796 RTP/AVP 8 0 6 3 5 101. a=rtpmap:8 PCMA/8000. a=rtpmap:0 PCMU/8000. a=rtpmap:6 DVI4/16000. a=rtpmap:3 GSM/8000. a=rtpmap:5 DVI4/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. m=video 35798 RTP/AVP 34 120. a=recvonly. a=rtpmap:34 H263/90000. a=rtpmap:120 h263/90000. # T XXX.XXX.152.78:1399 -> XXX.XXX.2.40:5060 [AP] ACK sip:userwm5@domain.net:5060;maddr=YYY.YYY.152.57;transport=tcp SIP/2.0. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-e063223a7b420f71-1--d87543-;rport. Max-Forwards: 70. Route: <sip:XXX.XXX.2.40;transport=tcp;lr;ftag=d37fe766;mproxy=yes;invite=tcp>. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 ACK. Proxy-Authorization: Digest username="usereb",realm="domain.net",nonce="440b877a9197230dccf837b9adb629fd8ebf8115",uri="sip:userwm5@domain.net",response="4b8c1425b2edd0c05302ec708a793316",algorithm=MD5. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 0. . # T XXX.XXX.2.40:42736 -> XXX.XXX.2.40:5060 [AP] ACK sip:XXX.XXX.2.40;transport=tcp;lr;ftag=d37fe766;mproxy=yes;invite=tcp SIP/2.0. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on>. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=0;i=535. Via: SIP/2.0/TCP XXX.XXX.152.78:5060;branch=z9hG4bK-d87543-e063223a7b420f71-1--d87543-;rport=1399. Max-Forwards: 69. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. From: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 2 ACK. Proxy-Authorization: Digest username="usereb",realm="domain.net",nonce="440b877a9197230dccf837b9adb629fd8ebf8115",uri="sip:userwm5@domain.net",response="4b8c1425b2edd0c05302ec708a793316",algorithm=MD5. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 0. . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.2.40:5060 -> XXX.XXX.153.42:8664 .... # U XXX.XXX.2.40:5060 -> 138.217.188.239:19110 .... # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # T YYY.YYY.152.57:2544 -> XXX.XXX.2.40:5060 [AP] BYE sip:XXX.XXX.2.40;transport=tcp;ftag=d37fe766;lr=on;mproxy=yes;invite=tcp SIP/2.0. Via: SIP/2.0/TCP YYY.YYY.152.57:5060. Max-Forwards: 70. From: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. To: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 BYE. Route: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. User-Agent: RTC/1.3. Content-Length: 0. . # T XXX.XXX.2.40:42737 -> XXX.XXX.152.78:5060 [AP] BYE sip:usereb@XXX.XXX.152.78:5060;transport=TCP SIP/2.0. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;ftag=0e106f3ac62449d0bc454368719020a8;lr=on>. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bKc5f.77604c67.0;i=435. Via: SIP/2.0/TCP YYY.YYY.152.57:5060. Max-Forwards: 69. From: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. To: "usereb"<sip:usereb@domain.net>;tag=d37fe766. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 BYE. User-Agent: RTC/1.3. Content-Length: 0. . # T XXX.XXX.152.78:1400 -> XXX.XXX.2.40:5060 [AP] SIP/2.0 200 OK. Via: SIP/2.0/TCP XXX.XXX.2.40;branch=z9hG4bKc5f.77604c67.0;i=435. Via: SIP/2.0/TCP YYY.YYY.152.57:5060. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;lr;ftag=0e106f3ac62449d0bc454368719020a8>. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: "usereb"<sip:usereb@domain.net>;tag=d37fe766. From: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 BYE. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 0. . # T XXX.XXX.2.40:5060 -> YYY.YYY.152.57:2544 [AP] SIP/2.0 200 OK. Via: SIP/2.0/TCP YYY.YYY.152.57:5060. Record-Route: <sip:XXX.XXX.2.40;transport=tcp;lr;ftag=0e106f3ac62449d0bc454368719020a8>. Contact: <sip:usereb@XXX.XXX.152.78:5060;transport=TCP>. To: "usereb"<sip:usereb@domain.net>;tag=d37fe766. From: <sip:userwm5@domain.net>;tag=0e106f3ac62449d0bc454368719020a8. Call-ID: 6f309543f11f7056@c3RnLWRlbGw.. CSeq: 1 BYE. User-Agent: CounterPath eyeBeam release 3013o stamp 23916. Content-Length: 0. . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . # U XXX.XXX.2.40:5060 -> XXX.XXX.153.42:8664 .... # U XXX.XXX.2.40:5060 -> 138.217.188.239:19110 .... # U XXX.XXX.153.42:8664 -> XXX.XXX.2.40:5060 . exit

18 years, 8 months

← Newer
1
...
37
38
39
40
41
42
43
...
51
Older →

Jump to page:

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 March 2006