sr-users

sr-users@lists.kamailio.org

28 participants
37537 discussions

[Users] proxy-authenticate causes phone to drop authenticate creds
by Mark Price 05 Apr '07

05 Apr '07

Hi, I am using openser 1.1.x as a front end to asterisk. Here is what happens in the dialog: 1. phone sends invite 2. openser says "Unauthorized" 3. phone sends invite + Authorization header 4. openser auths the packet and forwards to asterisk 5. asterisk says "proxy authentication required" 6. openser says "proxy authentication required" here is where it gets interesting. 7.a On some devices, the phone sends invite + Authorization header + Proxy-Authorizaiton header. 7.b On some devices, the phone sends invite + Proxy-Authorization header. How does one work around 7.b? Really, what I want to see is how to make it so that asterisk does not try to authenticate the call. However, since that doesn't seem to be possible, what is the sensible way to route these calls? Thanks, Mark Price

2 1

[Users] Authentication problem
by charl van vuuren 05 Apr '07

05 Apr '07

I'm trying to setup Openser (1.1) as registrar with mediaproxy and mysql all on the same box. I am currently using the SIP Proxy/Registrar with Mediaproxy config from sipwise. MySQL and Mediaproxy are running. Xlite registers successfully with Openser with the users I have created. The problem comes with the authentication. Both www_authorize and proxy_authorize fail. www_authorize fails at regtistration and proxy_authorize off course then fails when I try make a call. Any suggestions? Thanx

2 1

[Users] user agent in avp
by Mark Price 05 Apr '07

05 Apr '07

Hi, In openser 1.1.x, is it possible to get similar functionality to that suggested by the following: avp_check($hdr(ua[0]),"re/Some Phone UA/") thanks Mark Price

2 1

[Users] radius attributes
by Terry Robert 05 Apr '07

05 Apr '07

Hi openser, Following the tutorial on FreeRadius integration (http://www.openser.org/docs/openser-radius-1.0.x.html), I'm seeing accounting packets successfully sent to Radiusd. However, some attributes are missing, notably: UserName, CallingStationId, and CalledStationId. Radius client dictionary contains: ATTRIBUTE User-Name 1 string ATTRIBUTE Password 2 string ... ATTRIBUTE Called-Station-Id 30 string ATTRIBUTE Calling-Station-Id 31 string Output from 'radiusd -X' shows: ... Module: Instantiated detail (detail) Listening on authentication *:1812 Listening on accounting *:1813 Ready to process requests. rad_recv: Accounting-Request packet from host 10.10.90.198:32812, id=10, length=120 Acct-Status-Type = Start Service-Type = IAPP-Register Attr-102 = 0x000000c8 Error-Cause = 1 Event-Timestamp = "Apr 4 2007 15:10:27 PDT" Attr-105 = 0x3937333153495070546167303031 Attr-104 = 0x3937323853495070546167303131 Acct-Session-Id = "1-9731(a)10.10.90.51" NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 10.10.90.198 Processing the preacct section of radiusd.conf modcall: entering group preacct for request 0 modcall[preacct]: module "preprocess" returns noop for request 0 rlm_acct_unique: WARNING: Attribute User-Name was not found in request, unique ID MAY be inconsistent ... Any tips on how to fix this? Thanks.

1 0

RE: [Serusers] Problems with ACK
by Jiri Kuthan 04 Apr '07

04 Apr '07

I think the key message for problem analysis, client's ACK, is missing. This is the setting, right:? .100/UAC -----NAT/.248----> SER outbound @ .246 -----> UAS @ .239 The ACK in your message dump is only that one sent from proxy (246) to UAS (.239). The ACK which can possibly mismatch and produce the error message you mentioned must come from upstream. To be properly formatted, it must have Via identical to that of initial INVITE ( Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087) -jiri At 17:50 27/03/2007, Ricardo Martinez wrote: No. Time Source Destination Protocol Info > 14 6.102719 100.100.100.239 100.100.100.246 SIP Status: 487 Request Terminated >Session Initiation Protocol > Status-Line: SIP/2.0 487 Request Terminated > Status-Code: 487 > Resent Packet: False > Message Header > Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0 > Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087 >No. Time Source Destination Protocol Info > 15 6.103011 100.100.100.246 100.100.100.239 SIP Request: ACK sip:005622408196@100.100.100.239 >Session Initiation Protocol > Request-Line: ACK sip:005622408196@100.100.100.239 SIP/2.0 > Method: ACK > Resent Packet: False > Message Header > Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0 > f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403 > SIP Display info: "cl" > SIP from address: sip:cl@sipvoiss.desa.redvoiss.net > SIP tag: 1587516403 > i: <mailto:e94a98aa177e8579e5242a2091c0ac5f@192.168.1.100>e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100 > To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4 >Thanks > >Ricardo.- >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

3 4

[Serusers] error with CPL script( CPL module of SER)
by dillip parida 04 Apr '07

04 Apr '07

Hi all, I am trying to implement call redirection feature using cpl script. I have complied cpl module that supports the cpl script. I have uploaded the cpl script. plz help me to solve the problem.. I have written this mail regarding the error that > we are getting in testing the cpl script of Call redirection. > > We have three X-lite phones with SIP uris 2001(a)172.16.1.24, > ,2002(a)172.16.1.28 and 2003(a)172.16.1.31 and all the three soft phones > have been registered with SER proxy running on 10.2.3.123. All the > three users have added in the SER database along with mail ids. > > user mail id > 2001 2001(a)172.16.1.24 > 2002 2002(a)172.16.1.28 > 2003 2003(a)172.16.1.31 > > The call scenario is as follows.. > 1.user 2001 will make a call to user 2002. > 2. If the user 2002 is either not responding (No answer) or busy, then > the call > will be redirected to user 2003. > 3. we able to make a call to 2002,and user 2002's X-lite phone is > ringing but the call is > not getting redirected. > > The cpl script for redirection has been deployed in SER proxy. > > I am sending the call log of sip phone:2001 as an attachment along > with snapshot sip phone 2001. > > I am sending cpl script at the bottam of this mail.plz find the cpl script at the end of this mail. > As shown in the xlite screen "500 CPL script execution failed" can u > please suggest me if there is > any error in XML/CPL syntax. > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > <?xml version="1.0"?> > <!DOCTYPE html cpl PUBLIC "-//IETF//DTD RFCxxx CPL 1.0//EN" "cpl.dtd"> > <cpl> > <subaction id="pda"> > <location url="sip:2003@172.16.1.31 <sip:1003@172.16.1.31>"> > <proxy/> > </location> > </subaction> > <incoming> > <location url="sip:2002@172.16.1.28 <sip:1002@172.16.1.28>"> > <proxy timeout="8"> > <busy> > <sub ref="pda"/> > </busy> > <noanswer> > <sub ref="pda"/> > </noanswer> > </proxy> > </location> > </incoming> > </cpl>

1 0

Re: [Users] does openser support QoS ?
by NEILL WILKINSON 04 Apr '07

04 Apr '07

The more obvious question is: How does it know there is no more bandwidth available? As a signalling proxy, surely it has no visibility of the RTP usages or requirements. I guess if it counted all the complete INVITE-> OK dialogues and the SDP codec used it could estimate usage? But the RTP/media path could be different in each case of these so again the same question as above...... Neill...;o) ----- Original Message ---- From: Henning Westerholt <henning.westerholt(a)1und1.de> To: users(a)openser.org; yanlin <yanlin(a)fortinet.com> Sent: Tuesday, 3 April, 2007 10:41:31 AM Subject: Re: [Users] does openser support QoS ? On Tuesday 03 April 2007 11:15, yanlin wrote: > Hi, > > does openser support some kind of QoS ? > like, band width management, when there has no more usable bandwidth, then > new INVITE should be rejected. Hi Yanlin, if the bandwith is exceeded, no new INVITEs will get to the server and will timeout. :-) The "pike" module does some kind of DOS protection, but this is also no real QoS. There was a discussion two weeks ago about this topic on devel (the topic was "rand function in config file"), Klaus suggested some kind of bandwith management module there. But at the moment such a module don't exist in OpenSER. Cheers, Henning _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

1 0

[Users] New features added to OpenSer - BLA support and XMPP presence gateway
by Anca-Maria Vamanu 04 Apr '07

04 Apr '07

Two new modules were just introduced to SVN -- both are related to presence services. 1) pua_bla - implements Bridged Line Appearances according to the specifications in draft-anil-sipping-bla-03.txt. BLA, aka Shared Call/Line Appearance, comes from old telephony, where many devices share same line. Translated to SIP, means that many SIP devices share same AoR, but only one call can be established at a time, either addressed or initiated from the line. The call can be put on hold, and the others devices are notified so that they can pick up the call (the typical example is that with the secretary answering the call and putting it on hold to be picked up by the boss). The SIP devices must have client-side support for BLA as well. In out tests we used POLYCOM SoundPoint IP 430 SIP phones. The behaviour for this specific device: when picking up the handset form one phone a red light appears at the other phones. If attempting to call from a second phone using the same line, you get the message "Resources full". If a call is established, when putting it on hold, the light starts to flicker at the other phones and it is possible to pick it up. 2) pua_xmpp - is a presence gateway between SIMPLE and XMPP. It comes to complete the IM gateway, by enabling presence state information exchange between SIP/SIMPLE and Jabber/XMPP clients. For testings we used Gaim 2.0.0beta5, Psi v0.10 for XMPP and Xlite v3.0 for SIP. Some sample config file to implement above features will be published soon on dokuwiki.

1 0

RE: [Users] Problem with dialog module
by Leonid Fainshtein 04 Apr '07

04 Apr '07

Hi Bogdan, Please check the ngrep output. I put my comments along with the trace: 1. ****** The 203(a)172.17.4.22 calls 3525(a)172.17.4.22 U 2007/03/18 12:54:09.758887 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:3525@172.17.4.22:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060 ;branch=z9hG4bK3796032784-846..Max-Forwards: 70..Allow: INVITE,OPTIONS,CANC EL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip :3525@172.17.4.22:5060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..Contact: <sip:203@172.17.2.11:5060>..Content-Type: application/sdp..Proxy-Authorizat ion: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63 342cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b 864 a4ab937d17f42c7cd45a",algorithm=md5..Content-Length: 237....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 R TP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT/8000.. a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendrecv.. U 2007/03/18 12:54:09.766562 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.11:5060;branch=z9hG4bK3796032784-846..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>..Call-ID: 3795992784-84 6..CSeq: 2 INVITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-L ength: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 re q_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:3525@172.17.4.22:5060 out _uri=sip:3525@172.17.2.14;user=phone via_cnt==1".... U 2007/03/18 12:54:09.766871 172.17.4.22:5060 -> 172.17.2.14:5060 INVITE sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Via: SIP/2.0/UDP 172 .17.4.22;branch=z9hG4bKbd8b.80bd0bc3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3796032784-846..Max-Forwards: 69..Allow: INVITE,OPTIONS,CANCEL ,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS 3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3 525@172.17.4.22:5060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..Contact: <s ip:203@172.17.2.11:5060>..Content-Type: application/sdp..Content-Length: 23 7....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t= 0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TE LEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 v er2..a=sendrecv.. U 2007/03/18 12:54:09.772591 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0bc 3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5 060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..User-Agent: Grandstream BT11 0 1.0.8.16..Content-Length: 0.... U 2007/03/18 12:54:09.775043 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0b c3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..Recor d-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2> ..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.1 7.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE. .User-Agent: Grandstream BT110 1.0.8.16..Content-Length: 0.... U 2007/03/18 12:54:09.777250 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK379603 2784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;di d=55f.4491d5b2>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846.. CSeq: 2 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Content-Length: 0.. .. U 2007/03/18 12:54:13.673700 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0bc3.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Fro m: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.2 2:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE..User -Agent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=pho ne>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Cont ent-Type: application/sdp..Supported: replaces..Content-Length: 153....v=0. .o=3525 8000 8000 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 172.17.2.14..t=0 0..m=audio 5004 RTP/AVP 0..a=sendrecv..a=rtpmap:0 PCMU/8000..a=ptime:20.. U 2007/03/18 12:54:13.676298 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f .4491d5b2>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip: 3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.1 7.2.14:5060;user=phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS, INFO,SUBSCRIBE..Content-Type: application/sdp..Supported: replaces..Content -Length: 153....v=0..o=3525 8000 8000 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 172.17.2.14..t=0 0..m=audio 5004 RTP/AVP 0..a=sendrecv..a=rtpmap:0 PCMU /8000..a=ptime:20.. U 2007/03/18 12:54:13.721732 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:3525@172.17.2.14:5060;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2 .11:5060;branch=z9hG4bK3799992784-846..Route: <sip:172.17.4.22;lr=on;ftag=h ssUA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorizatio n: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c6334 2cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b86 4a4 ab937d17f42c7cd45a",algorithm=md5..User-Agent: Claro BS3202 A454..From: <si p:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060 >;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 ACK..Contact: <sip :203@172.17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:13.724056 172.17.4.22:5060 -> 172.17.2.14:5060 ACK sip:3525@172.17.2.14:5060;user=phone SIP/2.0..Record-Route: <sip:172.17 .4.22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch =z9hG4bKbd8b.80bd0bc3.2..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK37 99992784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613", realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri ="s ip:3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",al gor ithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 2 ACK..Contact: <sip:203@172.17.2.11:5060>..C ontent-Length: 0.... 2. ****** The call is established. The did=55f.4491d5b2. Now 3525(a)172.17.4.22 initiates call transfer. It sends re-INVITE in order to mute the call partner. The header filed Route contains did=55f.4491d5b2. U 2007/03/18 12:54:16.394546 172.17.2.14:5060 -> 172.17.4.22:5060 INVITE sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branc h=z9hG4bKb9469def476f37f2..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992 784-846;did=55f.4491d5b2>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae 245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3 525(a)172.17.2.14;user=phone>..Supported: replaces..Call-ID: 3795992784-846.. CSeq: 321 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70. .Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content- Type: application/sdp..Content-Length: 320....v=0..o=3525 8000 8001 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 0.0.0.0..t=0 0..m=audio 5004 RTP/AVP 0 8 18 4 99 2 9..a=sendonly..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpm ap:18 G729/8000..a=rtpmap:4 G723/8000..a=rtpmap:99 iLBC/8000..a=fmtp:99 mod e=20..a=rtpmap:2 G726-32/8000..a=rtpmap:9 G722/16000..a=ptime:20.. U 2007/03/18 12:54:16.396983 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.14;branch=z9hG4bKb9469def476f37f2..From: <sip:3525@172.17.4.22:5060>;tag =61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call -ID: 3795992784-846..CSeq: 321 INVITE..Server: ClaroSIS (Openser 1.1.1 (i38 6/linux))..Content-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=3997 req_src_ip=172.17.2.14 req_src_port=5060 in_uri=sip:203@1 72.17.2.11:5060 out_uri=sip:203@172.17.2.11:5060 via_cnt==1".... 3. ****** OpenSer sends the re-INVITE to the transferee. Please note, that "did" doesn't appear in the Record-Route. As result of that, BYE for this call will no have "did" parameter and the dialog will appear as not closed. U 2007/03/18 12:54:16.397307 172.17.4.22:5060 -> 172.17.2.11:5060 INVITE sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr= on;ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751. 82bc6f96.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2..Fr om: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4 .22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>.. Supported: replaces..Call-ID: 3795992784-846..CSeq: 321 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..Allow: INVITE,ACK,CANCEL,BYE ,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Type: application/sdp..Conten t-Length: 320....v=0..o=3525 8000 8001 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 0.0.0.0..t=0 0..m=audio 5004 RTP/AVP 0 8 18 4 99 2 9..a=sendonly..a=rt pmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:4 G 723/8000..a=rtpmap:99 iLBC/8000..a=fmtp:99 mode=20..a=rtpmap:2 G726-32/8000 ..a=rtpmap:9 G722/16000..a=ptime:20.. U 2007/03/18 12:54:16.435210 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751.82bc6f96.0, SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2..Record-Route: <sip: 172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Claro BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 321 INVITE..Conta ct: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK, INFO,REFER,NOTIFY..Content-Type: application/sdp..Content-Length: 167....v= 0..o=Claro 1174230681570 1174230681 IN IP4 172.17.2.11..s=Claro..c=IN IP4 1 72.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0..a=rtpmap:0 PCMU/8000..a=ptime:2 0..a=recvonly.. U 2007/03/18 12:54:16.436772 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Clar o BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CS eq: 321 INVITE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS, CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Content-Type: application/sdp..Cont ent-Length: 167....v=0..o=Claro 1174230681570 1174230681 IN IP4 172.17.2.11 ..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0..a=rtpmap:0 PCMU/8000..a=ptime:20..a=recvonly.. U 2007/03/18 12:54:16.443328 172.17.2.14:5060 -> 172.17.4.22:5060 ACK sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z 9hG4bK26b04409b72e06f9..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55 >..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172 .17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=pho ne>..Call-ID: 3795992784-846..CSeq: 321 ACK..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIO NS,INFO,SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:16.445463 172.17.4.22:5060 -> 172.17.2.11:5060 ACK sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=on; ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751.82b c6f96.2..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK26b04409b72e06f9..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>..Cal l-ID: 3795992784-846..CSeq: 321 ACK..User-Agent: Grandstream BT110 1.0.8.16 ..Max-Forwards: 69..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO, SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:20.272078 172.17.2.14:5060 -> 172.17.4.22:5060 REFER sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch =z9hG4bK9e02f3ad995f8245..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b 55>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@1 72.17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=p hone>..Supported: replaces..Refer-To: <sip:5524@172.17.4.22;user=phone>..Re ferred-By: <sip:3525@172.17.4.22;user=phone>..Call-ID: 3795992784-846..CSeq : 322 REFER..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allo w: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Lengt h: 0.... U 2007/03/18 12:54:20.275997 172.17.4.22:5060 -> 172.17.2.11:5060 REFER sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK1751.e 223fee7.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad995f8245..Fro m: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4. 22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>..S upported: replaces..Refer-To: <sip:5524@172.17.4.22;user=phone>..Referred-B y: <sip:3525@172.17.4.22;user=phone>..Call-ID: 3795992784-846..CSeq: 322 RE FER..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:20.323290 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806597784-846..Max-Forwards: 70..Allow: INVITE,OPTION S,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:2 03(a)172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=ph one>..Call-ID: 3806597784-846..CSeq: 1 INVITE..Contact: <sip:203@172.17.2.1 1:5060>..Referred-By: <sip:3525@172.17.4.22;user=phone>..Content-Type: appl ication/sdp..Content-Length: 237....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s= Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpm ap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpma p:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendrecv.. U 2007/03/18 12:54:20.324935 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 172.17.2.11:506 0;branch=z9hG4bK3806597784-846..From: <sip:203@172.17.4.22>;tag=hssUA_38065 97784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=329cfeaa6ded039da25ff8 cbb8668bd2.dc60..Call-ID: 3806597784-846..CSeq: 1 INVITE..Proxy-Authenticat e: Digest realm="172.17.4.22", nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9 f2c"..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-Length: 0..War ning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4001 req_src_ip=172. 17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=si p:5524@172.17.4.22;user=phone via_cnt==1".... U 2007/03/18 12:54:20.328647 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK1751.e223f ee7.0,SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad995f8245..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..From: <sip:3525@172.17.4.22 :5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784 -846..Call-ID: 3795992784-846..CSeq: 322 REFER..Contact: <sip:203@172.17.2. 11:5060>..Content-Length: 0.... U 2007/03/18 12:54:20.330099 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad99 5f8245..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 322 REFER..Contac t: <sip:203@172.17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:20.351529 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5 060;branch=z9hG4bK3806597784-846..Max-Forwards: 70..User-Agent: Claro BS320 2 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524 @172.17.4.22;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.dc60..Call -ID : 3806597784-846..CSeq: 1 ACK..Contact: <sip:203@172.17.2.11:5060>..Content -Length: 0.... U 2007/03/18 12:54:20.364969 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806642784-846..Max-Forwards: 70..Allow: INVITE,OPTION S,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To : <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVIT E..Contact: <sip:203@172.17.2.11:5060>..Content-Type: application/sdp..Prox y-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fe80 721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524@172.17.4.22",response="3f b20 f7d6e67668e07b862b99412162d",algorithm=md5..Content-Length: 237....v=0..o=C laro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT /8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendre cv.. U 2007/03/18 12:54:20.372610 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.11:5060;branch=z9hG4bK3806642784-846..From: <sip:203@172.17.4.22>;tag=hs sUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597 784-846..CSeq: 2 INVITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Con tent-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4 003 req_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;us er=phone out_uri=sip:5524@172.17.2.168:5061 via_cnt==1".... U 2007/03/18 12:54:20.372833 172.17.4.22:5060 -> 172.17.2.168:5061 INVITE sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;l r=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Via: SIP/2.0/UDP 172.17.4. 22;branch=z9hG4bK95c6.337d9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch= z9hG4bK3806642784-846..Max-Forwards: 69..Allow: INVITE,OPTIONS,CANCEL,ACK,B YE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A 454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@17 2.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVITE..Contact: <s ip:203@172.17.2.11:5060>..Content-Type: application/sdp..Content-Length: 23 7....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t= 0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TE LEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 v er2..a=sendrecv.. U 2007/03/18 12:54:20.385872 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 100 Trying..To: <sip:5524@172.17.4.22;user=phone>..From: <sip:203@1 72.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVI TE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6.337d9f56.0..Via: SIP/2. 0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846..Record-Route: <sip:172 .17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Server: Linksys/ PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.393629 172.17.2.11:5060 -> 172.17.4.22:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806672784-846..Route: <sip:172.17.4.22;lr=on;ftag=hss UA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342c c574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a 4ab 937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK ,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 3 NOTIFY..Contact: <sip:203@172.17.2.11:5060> ..Event: refer..Subscription-State: active;expires=60..Content-Type: messag e/sipfrag..Content-Length: 530....SIP/2.0 100 trying -- your call is import ant to us..Via: SIP/2.0/UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9 hG4bK3806642784-846..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846.. To: <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INV ITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-Length: 0..Warn ing: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 req_src_ip=172.1 7.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=sip :5524@172.17.2.168:5061 via_cnt==1".... U 2007/03/18 12:54:20.396980 172.17.4.22:5060 -> 172.17.2.14:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z 9hG4bKcd8b.81aaa3f3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 672784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613",re alm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri=" sip :3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",algo rit hm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Suppo rted: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: < sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..C Seq: 3 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..Subscript ion-State: active;expires=60..Content-Type: message/sipfrag..Content-Length : 530....SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/U DP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..From : <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22 ;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVITE..Server: ClaroSIS (Op enser 1.1.1 (i386/linux))..Content-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 req_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=sip:5524@172.17.2.168:5061 v ia_cnt==1".... U 2007/03/18 12:54:20.401630 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff 0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806 597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6 .337d9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c 5bd92>..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.403183 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff 0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806 597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4b K3806642784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784 -846;did=0e3.7c5bd92>..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0... . U 2007/03/18 12:54:20.403878 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKcd8b.81aaa3f3.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806672784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 3 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:20.407617 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806672784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 3 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... U 2007/03/18 12:54:20.429109 172.17.2.11:5060 -> 172.17.4.22:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806702784-846..Route: <sip:172.17.4.22;lr=on;ftag=hss UA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342c c574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a 4ab 937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK ,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 4 NOTIFY..Contact: <sip:203@172.17.2.11:5060> ..Event: refer..Subscription-State: active;expires=60..Content-Type: messag e/sipfrag..Content-Length: 397....SIP/2.0 180 Ringing..To: <sip:5524@172.17 .4.22;user=phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=h ssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/ UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..Rec ord-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92 >..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.431776 172.17.4.22:5060 -> 172.17.2.14:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z 9hG4bK9d8b.47c7ce13.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 702784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613",re alm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri=" sip :3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",algo rit hm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Suppo rted: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: < sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..C Seq: 4 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..Subscript ion-State: active;expires=60..Content-Type: message/sipfrag..Content-Length : 397....SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb 5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call -ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;rece ived=172.17.4.22;branch=z9hG4bK3806642784-846..Record-Route: <sip:172.17.4. 22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Server: Linksys/PAP2-3 .1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.438291 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK9d8b.47c7ce13.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806702784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 4 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:20.439954 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806702784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 4 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... U 2007/03/18 12:54:23.312128 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6.337d 9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846..Rec ord-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92 >..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksys/PAP2-3.1.3(L S)..Content-Length: 210..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPT IONS, REFER..Supported: x-sipura..Content-Type: application/sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168..t=0 0.. m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-e vent/8000..a=fmtp:101 0-15..a=ptime:30..a=sendrecv.. U 2007/03/18 12:54:23.313878 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 642784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846; did=0e3.7c5bd92>..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Links ys/PAP2-3.1.3(LS)..Content-Length: 210..Allow: ACK, BYE, CANCEL, INFO, INVI TE, NOTIFY, OPTIONS, REFER..Supported: x-sipura..Content-Type: application/ sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17 .2.168..t=0 0..m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap: 101 telephone-event/8000..a=fmtp:101 0-15..a=ptime:30..a=sendrecv.. U 2007/03/18 12:54:23.355581 172.17.2.11:5060 -> 172.17.4.22:5060 27646@0:1480 ........NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 17 2.17.2.11:5060;branch=z9hG4bK3809632784-846..Route: <sip:172.17.4.22;lr=on; ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Author ization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f 9c63342cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156e a61 b864a4ab937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,B YE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae2 45b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..Contact: <sip:203@172.17.2. 11:5060>..Event: refer..Subscription-State: terminated;reason=noresource..C ontent-Type: message/sipfrag..Content-Length: 756....SIP/2.0 200 OK..To: <s ip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172. 17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE. .Via: SIP/2.0/UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK38066 42784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;d id=0e3.7c5bd92>..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksy s/PAP2-3.1.3(LS)..Content-Length: 210..Allow: ACK,BYE,CANCEL,INFO,INVITE,NO TIFY,OPTIONS,REFER..Supported: x-sipura..Content-Type: application/sdp....v =0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168.. t=0 0..m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/800 U 2007/03/18 12:54:23.361462 172.17.4.22:5060 -> 172.17.2.14:5060 50085@0:1480 .....I..NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip: 172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22; branch=z9hG4bKad8b.016fb321.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9h G4bK3809632784-846..Max-Forwards: 69..Proxy-Authorization: Digest username= "613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3c a", uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd4 5a" ,algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIF Y..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-84 6..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 379599278 4-846..CSeq: 5 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..S ubscription-State: terminated;reason=noresource..Content-Type: message/sipf rag..Content-Length: 756....SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user= phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_380659 7784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17. 2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..Record-Rout e: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Conta ct: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksys/PAP2-3.1.3(LS)..Content -Length: 210..Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER..Suppo rted: x-sipura..Content-Type: application/sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168..t=0 0 U 2007/03/18 12:54:23.371944 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:5524@172.17.2.168:5061 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3809647784-846..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_38065 97784-846;did=0e3.7c5bd92>..Max-Forwards: 70..Proxy-Authorization: Digest u sername="613",realm="172.17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66 ef8 8b9f2c",uri="sip:5524@172.17.4.22",response="3fb20f7d6e67668e07b862b9941 216 2d",algorithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.2 2>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5 cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 2 ACK..Contact: <sip:203@172 .17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:23.372334 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKad8b.016fb321.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809632784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:23.373917 172.17.4.22:5060 -> 172.17.2.168:5061 ACK sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=hssUA_3806597784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95 c6.337d9f56.2..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809647784-8 46..Max-Forwards: 69..Proxy-Authorization: Digest username="613",realm="172 .17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524 @17 2.17.4.22",response="3fb20f7d6e67668e07b862b99412162d",algorithm=md5..Us er- Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784- 846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 2 ACK..Contact: <sip:203@172.17.2.11:5060>..Content- Length: 0.... U 2007/03/18 12:54:23.375179 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809632784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... 4. ****** The message BYE doesn't have the did parameter. U 2007/03/18 12:54:23.490685 172.17.2.14:5060 -> 172.17.4.22:5060 BYE sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z 9hG4bKa419f2aaf11a7b40..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55 >..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172 .17.4.22>;tag=hssUA_3795992784-846..Supported: replaces..Call-ID: 379599278 4-846..CSeq: 323 BYE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Cont ent-Length: 0.... U 2007/03/18 12:54:23.494656 172.17.4.22:5060 -> 172.17.2.11:5060 BYE sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=on; ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK2751.609 47d11.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..Supported: replaces..Call-ID: 3795992784-846..C Seq: 323 BYE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..All ow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Leng th: 0.... U 2007/03/18 12:54:23.517688 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK2751.60947d11.0, SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40..Record-Route: <sip: 172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Claro BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 323 BYE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INF O,REFER,NOTIFY..Content-Length: 0.... U 2007/03/18 12:54:23.519138 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Clar o BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CS eq: 323 BYE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CAN CEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Content-Length: 0.... U 2007/03/18 12:54:29.780666 172.17.2.11:5060 -> 172.17.4.22:5060 BYE sip:5524@172.17.2.168:5061 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3816062784-846..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_38065 97784-846;did=0e3.7c5bd92>..Max-Forwards: 70..Proxy-Authorization: Digest u sername="613",realm="172.17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66 ef8 8b9f2c",uri="sip:5524@172.17.4.22",response="3fb20f7d6e67668e07b862b9941 216 2d",algorithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.2 2>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5 cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 3 BYE..Content-Length: 0.... U 2007/03/18 12:54:29.784698 172.17.4.22:5060 -> 172.17.2.168:5061 BYE sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=hssUA_3806597784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKa5 c6.704043c7.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062784-8 46..Max-Forwards: 69..Proxy-Authorization: Digest username="613",realm="172 .17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524 @17 2.17.4.22",response="3fb20f7d6e67668e07b862b99412162d",algorithm=md5..Us er- Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784- 846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 3 BYE..Content-Length: 0.... U 2007/03/18 12:54:29.804689 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 3 BYE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKa5c6.704043c 7.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062784-846..Record -Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846>..Server: Linksys/ PAP2-3.1.3(LS)..P-RTP-Stat: PS=146,OS=34640,PR=303,OR=48162,PL=1,JI=0,LA=10 ,DU=6,EN=G711u,DE=G711u..Content-Length: 0.... U 2007/03/18 12:54:29.806174 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 3 BYE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062 784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846>..S erver: Linksys/PAP2-3.1.3(LS)..P-RTP-Stat: PS=146,OS=34640,PR=303,OR=48162, PL=1,JI=0,LA=10,DU=6,EN=G711u,DE=G711u..Content-Length: 0.... As you can see, the dialog (callid=3795992784-846) still exists... /usr/local/sbin/openserctl fifo dlg_list 200 OK hash=3925, label=727521604, ptr=0x405c2d78 state=3, timeout=236218 callid='3795992784-846' from uri='sip:203@172.17.4.22', tag='hssUA_3795992784-846' to uri='sip:3525@172.17.4.22:5060', tag='61645575ae245b55' Thnk you in advance, Leonid Fainshtein -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: Friday, March 16, 2007 2:51 PM To: Leonid Fainshtein Cc: users(a)openser.org Subject: Re: [Users] Problem with dialog module Hi Leonid, what do you mean by "removes"?. When sequential requests are processed, the Route header corresponding to your server will be completely removed. regards, bogdan Leonid Fainshtein wrote: > Hi, > I see that when Openser 1.1 receives re-INVITE it removes parameter > "did=" from header field Route before sending it to the second call > party. > Any idea? > > Thank you in advance, > Leonid > > > ******************************************** > This outgoing mail message was scanned by McAfee GroupShield Engine > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users > > ******************************************** This outgoing mail message was scanned by McAfee GroupShield Engine

2 2

[Serusers] SER with TLS
by Katty Xiong 04 Apr '07

04 Apr '07

I am using SER ottendorf with TLS protocol and have the following issues. Does anybody experience similar problems? SER cannot run with the following setup in the configuration file: (I follow this link to setup key and certificate: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/tls/README…) modparam("tls", "private_key", "cakey.pem") modparam("tls", "certificate", "cacert.pem") modparam("tls", "ca_list", "calist.pem") modparam("tls", "cipher_list", "HIGH"); With the last line commented out: #modparam("tls", "cipher_list", "HIGH"); SER can start, but the tls connection cannot be established. Network trace shows SER does not responde to ClientHello sent by client. Thanks, Joy ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367

3 9

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