sr-users July 2008

sr-users@lists.kamailio.org

147 participants
207 discussions

Re: [OpenSER-Users] About openser redirect - forward
by Iñaki Baz Castillo 25 Jul '08

25 Jul '08

El Viernes, 20 de Junio de 2008, Valerio Di Marino escribió: > Thanks for your answer. Ok, but next time continue the thread in the maillist ;) > 2008/6/20 Iñaki Baz Castillo ibc(a)aliax.net: > > AFAIK if a UAC is redirected it will not include the already used > > credentials > > in the new request to the new destination (maybe I'm wrong). > > Do you think is possible to force using the pseudovariables ? No, it's not possible. When a UAAC receives a 302 it generates a completely new request with destination the URI of the "Contact" in the 302. > > If you need solving NAT in your OpenSer then you need to forward the > > request > > in it after make fix NAT. > > How ? Can explain better ? If a UAC receives a 302 it will generate a new INVITE. If the UAC has not configured your OpenSer as outbound proxy, the new INVITE it generates will go directly to the SIP provider, so it's not possible your OpenSer makes fix the NAT (fix "Contact" and so). But maybe your SIP provider makes fix the NAT by itself, or you can try STUN in your UAC's. > > If not you could use forwarding or redirect. > > With redirect, openser will send an address and the uer will contact the > new address: is it correct ? (I am not shure). Yes, OpenSer replies a 302 with the new URI in the "Contact" header. > > In OpenSer to get a redirection you must set the RURI ($ru = ...) and > > reply a > > 302 to the user. > > Can you send ma a routine syntax ? > For example, I would redirect to sip.voipstunt.com Something like: $ru = "sip.voipstunt.com"; send_reply("302", "Redirect to SIP provider"); exit; -- Iñaki Baz Castillo

4 6

[OpenSER-Users] Intervention in provisional responses of stateful INVITE processing.
by Alex Balashov 25 Jul '08

25 Jul '08

Greetings, An OpenSER REQUEST-ROUTE that statefully t_relay()s an INVITE request will automatically pass back a provisional "100 Trying" response to the sender. The problem I have is that I have a database operation that occurs in my main REQUEST-ROUTE that can potentially, under certain unfavourable circumstances, be somewhat latent. This operation must run before the relaying can occur, since its results are used to rewrite the RURI, etc. When the operation lags, sometimes it exhausts the T-timers and results in retransmission of the INVITE, or, for equipment configured in a particularly conservative way, even a failure. So, what I need is some way to pass a provisional "100 Trying" at the beginning of the REQUEST-ROUTE immediately in order to placate the sender. I can't just reply statelessly, because I need the stateful processing for other things related to call accounting, so I must use 'tm.' And if I send a stateless "100 Trying" reply, the subsequent t_relay() will not know that and duplicate it, and although as far as I know this does not violate the RFC, it is still a situation I would like to avoid in principle. What I need to know is if there is some way in 'tm' to disable automatic provisional responses in a temporary or ephemeral fashion, or else to disable them entirely and then re-enable them later. Thank you so much in advance for all of your help! -- Alex -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599

2 2

[OpenSER-Users] Why 'sip_trace' desn't show ACK for a "200 OK" from OpenSer to UAS?
by Iñaki Baz Castillo 24 Jul '08

24 Jul '08

(Sorry, I sent this mail to devel maillist) Hi, the first I do in my OpenSer script is: -------------------------------------------------------- modparam("siptrace", "trace_flag", FLAG_SIPTRACE) modparam("siptrace", "trace_on", 1) route { ### SipTrace. if ! is_method("OPTIONS|REGISTER") { sip_trace(); setflag(FLAG_SIPTRACE); } ... -------------------------------------------------------- When an INVITE gets a 200 OK the UAC sends an ACK (end to end). This ACK from UAC to OpenSer is stored in 'sip_trace' table, but the same ACK from OpenSer to the UAS (in-dialog ACK) is not stored, why? Is there any reason for this? AFAIK this ACK is like any in-dialog request and 'sip_trace' stores correctly both legs of any in-dialog request, except in the case of an ACK for a 200 OK. Since the "special" treatment OpenSer performs in the ACK, maybe there is a technical issue that makes imposible ACK from OpenSer to UAS to appear in "sip_trace"? Thanks. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

3 2

[OpenSER-Users] Identifying call branches for multiple contacts.
by Alex Balashov 24 Jul '08

24 Jul '08

Greetings, If I have multiple contacts registered concurrently for one binding with the usrloc/registrar modules, is there a way I can get a count for, or iteratively traverse somehow, the call branches created when a request goes out to that binding? In other words, if I have UAC A and UAC B sharing a binding, is there some way I can access the distinct call paths programmatically within the route plan? Thanks! -- Alex Balashov Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671 Mobile : (+1) (706) 338-8599

2 1

[OpenSER-Users] integrating OpenSER + RTPproxy for recording the conservation
by LetMeKnow 24 Jul '08

24 Jul '08

Hello user's OpenSER and RTPproxy Am to integrate the openser and rtprpxy for live recording of converstions. Am just to try to how to do the recording in openser and rtpprpxy Am using openser-1.3.2 and Rtpproxy-1.2 . in my Lab, means proxy and UAC's all are in internal LAN. In openser.cfg if ( method=="INVITE") { force_rtp_proxy(); start_recording(); t_on_reply("1"); t_relay(); exit; } onroute_reply[1] { if (status=="200") force_rtp_proxy(); } when i observer in Rtp Proxy in debug mode. I got this : received command "16034_2 U 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg. 192.168.4.6229334 f0007919;1" new session 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg., tag f0007919;1 requested, type strong hash_table_append: hash(26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg.) = 168 new session on a port 35004 created, tag f0007919;1 pre-filling caller's address with 192.168.4.62:29334 sending reply "16034_2 35004 192.168.4.102 " received command "16034_3 L 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg. 192.168.4.2382650 f0007919;1 1f668e3e;1" lookup on ports 35004/35006, session timer restarted pre-filling callee's address with 192.168.4.238:2650 sending reply "16034_3 35006 192.168.4.102 " received command "16034_4 R 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg. 1f668e3e f0007919" record request failed: session 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg., tags 1f668e3e/f0007919 not found sending reply "16034_4 E8 " received command "16034_5 D 26685862e1635844MGYwNDNmODM0MjM0YTIwNWY3Mzc2NzZiZjQwYTJhNzg. f0007919 1f668e3e" forcefully deleting session 1 on ports 35004/35006 RTP stats: 0 in from callee, 6 in from caller, 6 relayed, 0 dropped RTCP stats: 2 in from callee, 2 in from caller, 4 relayed, 0 dropped session on ports 35004/35006 is cleaned up sending reply "16034_5 0 " Audio is fine on both UAC side. problem in its starting and when i use start_recording. Thanks &Regards Ravi Prakash Sunkara VoIP Development Tech Lead 91-9999882776

2 2

Re: [OpenSER-Users] openser + mysql clusters
by Stanisław Pitucha 24 Jul '08

24 Jul '08

----- "Sajith T S" <sajith(a)gmail.com> wrote: > How is the overall experience like re. deploying openser with mysql > clusters? Good enough. Just setup A record pointing at 2 or more api nodes and set them up with virtual ips (heartbeat works quite well...). Openser will recover if one of the nodes fail. > Are there gotchas etc that need to be taken care of? (For > example, a 2006 article [1] says that "The MySQL NDB engine currently > runs its database completely in memory. This means that you have to > be > able to fit your database in memory." But this is not documented as > a > limitation in mysql faq.) It's a feature and it's in the first sentence of cluster overview: "... enables clustering of in-memory databases" ;) Gotchas: - don't bother with 5.0 - it's got strange issues - 5.1.23 was the last version of 5.1.X with ndb. Now you have to compile carrier grade edition from source. - ping database once in a while (every database in a cluster) by *writing* to some table. ndb sometimes just locks itself, but allows selects (locks internally - I've never used lock statements). Restarting api node is enough in that case. - No schema change needed - it just works with standard tables. - Inserts / updates will be slower - not much, but anyway. - hang out in #mysql-ndb channel on freenode -> you'll learn some magic ndb-mgm commands which are sometimes not documented. Otherwise, it's not that different from a standard mysql database. --- Stan

6 8

[OpenSER-Users] Presence & XML DTD Namespace Error
by Ross Beer 24 Jul '08

24 Jul '08

Hi, I am using the presence_xml module to provide presence across multiple clients. X-Lite, Bria works well however Snom phones produce the following error: ------------- ERROR ---------------- namespace error : Namespace prefix hs on detected-state is not defined <hs:detected-state>Lunch</hs:detected-state> ^namespace error : Namespace prefix hs on device is not definedtact priority="0.000">sip:--- ADDRESS ----</contact> <hs:device ^namespace error : Namespace prefix hs on caption is not defined <hs:caption>snom370</hs:caption> ^namespace error : Namespace prefix hs on detected-state is not defined <hs:detected-state>Busy</hs:detected-state> ^namespace error : Namespace prefix hs on device is not definedtact priority="0.000">sip:--- ADDRESS ----</contact> <hs:device ^namespace error : Namespace prefix hs on caption is not defined <hs:caption>snom370</hs:caption> ^namespace error : Namespace prefix hs on detected-state is not defined <hs:detected-state>Lunch</hs:detected-state> ^namespace error : Namespace prefix hs on device is not definedtact priority="0.000">sip:--- ADDRESS ----</contact> <hs:device ^namespace error : Namespace prefix hs on caption is not defined <hs:caption>snom370</hs:caption> ^ ------------- END ERROR ---------------- It looks like a validation issue with the XML, is there anyway you can switch off validation or update the DTD? Thanks, Ross _________________________________________________________________ Invite your Facebook friends to chat on Messenger http://clk.atdmt.com/UKM/go/101719649/direct/01/

1 0

[OpenSER-Users] Firewall causes ERROR:tm:msg_send: udp_send failed
by CSB 24 Jul '08

24 Jul '08

I have an error which is driving me crazy: Jul 24 16:58:34 beta /sbin/openser[5446]: ERROR:core:udp_send: sendto(sock,0x81aaed8,825,0,0xb61216f0,16): Operation not permitted(1) Jul 24 16:58:34 beta /sbin/openser[5446]: ERROR:tm:msg_send: udp_send failed This is firewall related because when I turn iptables off the problem goes away. But although all ACCEPT and DENY messages are logged by the firewall, there is no corresponding message logged. When a call is made between two UACs and the far end attempts to answer the call, the call is not answered successfully. The dialogue is shown below. If I turn the firewall off, start a call and then turn the firewall on the call continues successfully. However the next call is not successful. We use Mediaproxy and I suspect that is trying to do some communication that is being blocked by the firewall but that is only a suspicion. The dialogue for this call is shown at the bottom. When comparing these two dialogues with the firewall turned on: - when the callee answers, OpenSER receives a 200 OK but doesn't immediately pass that on to the caller - after a number of 200 messages from the callee, OpenSER sends the 200 to the caller but the Contact is the private IP address whereas when the firewall is turned off it is the public IP address I have also included the iptables config. Note that some lines are commented out due to the testing I'm doing and IP addresses have been changed. Any advice on the changes required would be appreciated. Thanks **************************** SIP dialogue with firewall on U 58.28.001.001:5060 -> 147.202.001.001:5060INVITE sip:44556644@domain.com:5060;user=phone SIP/2.0..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bK31ee9ba27B17140D..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Supported: 100rel,replaces..Allow-Events: talk,hold,conference..Max-Forwards: 70..Content-Type: application/sdp..Content-Length: 251....v=0..o=- 1216790239 1216790239 IN IP4 192.168.1.102..s=Polycom IP Phone..c=IN IP4 192.168.1.102..t=0 0..m=audio 2222 RTP/AVP 0 8 18 101..a=sendrecv..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:101 telephone-event/8000.. U 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 100 Giving a try..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bK31ee9ba27B17140D;rport=5060;received=58.28.001.0 01..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Server: OpenSER (1.3.2-notls (i386/linux))..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065INVITE sip:44556644@192.168.1.124:5065 SIP/2.0..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Supported: 100rel,replaces..Allow-Events: talk,hold,conference..Max-Forwards: 69..Content-Type: application/sdp..Content-Length: 253....v=0..o=- 1216790239 1216790239 IN IP4 192.168.1.102..s=Polycom IP Phone..c=IN IP4 147.202.001.001..t=0 0..m=audio 35982 RTP/AVP 0 8 18 101..a=sendrecv..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:101 telephone-event/8000.. U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 100 Trying..To: <sip:44556644@domain.com;user=phone>..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 180 Ringing..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 180 Ringing..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5060 -> 147.202.001.001:5060ACK sip:44556644@192.168.1.124:5065 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bK4b4d0d4aF803AD55..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..CSeq: 1 ACK..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Max-Forwards: 70..Content-Length: 0.... U 147.202.001.001:5060 -> 192.168.1.124:5065ACK sip:44556644@192.168.1.124:5065 SIP/2.0..Record-Route: <sip:147.202.001.001;lr=on;ftag=566CA8D1-4C8E0458>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK4b4d0d4aF803AD55..Via: SIP/2.0/UDP 192.168.1.102;received=58.28.001.001;branch=z9hG4bK4b4d0d4aF803AD55..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..CSeq: 1 ACK..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Max-Forwards: 69..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bK07da.73971d95.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..From: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bK31ee9ba27B1714 0D..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 298748 298748 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16424 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 58.28.001.001:5065 -> 147.202.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.124:5065;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 70..Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Record-Route: <sip:147.202.001.001;lr=on;ftag=e07209dc8d8de14fi5>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKc0cc.a198b237.0..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 69..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5060 -> 147.202.001.001:5060SIP/2.0 200 OK..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKc0cc.a198b237.0..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..CSeq: 101 BYE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Record-Route: <sip:147.202.001.001;lr=on;ftag=e07209dc8d8de14fi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..CSeq: 101 BYE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Record-Route: <sip:147.202.001.001;lr=on;ftag=e07209dc8d8de14fi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.124:5065;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 70..Route: <sip:147.202.001.001:5060;nat=yes;ftag=566CA8D1-4C8E0458;lr=on>..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-947b0ac7..From: <sip:44556644@domain.com;user=phone>;tag=e07209dc8d8de14fi5..To: "CSB" <sip:44556648@domain.com>;tag=566CA8D1-4C8E0458..CSeq: 101 BYE..Call-ID: 7f806604-ea80e337-e14b8216@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Record-Route: <sip:147.202.001.001;lr=on;ftag=e07209dc8d8de14fi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... ************************************** SIP dialogue with Firewall off U 58.28.001.001:5060 -> 147.202.001.001:5060INVITE sip:44556644@domain.com:5060;user=phone SIP/2.0..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bKca52e47AD4AD366..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Supported: 100rel,replaces..Allow-Events: talk,hold,conference..Max-Forwards: 70..Content-Type: application/sdp..Content-Length: 251....v=0..o=- 1216790431 1216790431 IN IP4 192.168.1.102..s=Polycom IP Phone..c=IN IP4 192.168.1.102..t=0 0..m=audio 2224 RTP/AVP 0 8 18 101..a=sendrecv..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:101 telephone-event/8000.. U 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 100 Giving a try..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bKca52e47AD4AD366;rport=5060;received=58.28.001.00 1..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Server: OpenSER (1.3.2-notls (i386/linux))..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065INVITE sip:44556644@192.168.1.124:5065 SIP/2.0..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..To: <sip:44556644@domain.com;user=phone>..CSeq: 1 INVITE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Supported: 100rel,replaces..Allow-Events: talk,hold,conference..Max-Forwards: 69..Content-Type: application/sdp..Content-Length: 253....v=0..o=- 1216790431 1216790431 IN IP4 192.168.1.102..s=Polycom IP Phone..c=IN IP4 147.202.001.001..t=0 0..m=audio 35984 RTP/AVP 0 8 18 101..a=sendrecv..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:101 telephone-event/8000.. U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 100 Trying..To: <sip:44556644@domain.com;user=phone>..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 180 Ringing..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 180 Ringing..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 317989 317989 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16426 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 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Contact: <sip:44556644@58.28.001.001:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 209..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 317989 317989 IN IP4 192.168.1.124..s=-..c=IN IP4 147.202.001.001..t=0 0..m=audio 35984 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 58.28.001.001:5060 -> 147.202.001.001:5060ACK sip:44556644@58.28.001.001:5065 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.102;branch=z9hG4bK9bb7064fBA56088E..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..CSeq: 1 ACK..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Max-Forwards: 70..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065ACK sip:44556644@58.28.001.001:5065 SIP/2.0..Record-Route: <sip:147.202.001.001;lr=on;ftag=3D7BF99A-F3B3ACE5>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.2..Via: SIP/2.0/UDP 192.168.1.102;received=58.28.001.001;branch=z9hG4bK9bb7064fBA56088E..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..CSeq: 1 ACK..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Max-Forwards: 69..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKf294.1cda4646.0..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Contact: <sip:44556644@192.168.1.124:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 208..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 317989 317989 IN IP4 192.168.1.124..s=-..c=IN IP4 192.168.1.124..t=0 0..m=audio 16426 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 147.202.001.001:5060 -> 58.28.001.001:5060SIP/2.0 200 OK..To: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..From: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 1 INVITE..Via: SIP/2.0/UDP 192.168.1.102;rport=5060;received=58.28.001.001;branch=z9hG4bKca52e47AD4AD36 6..Record-Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..Contact: <sip:44556644@58.28.001.001:5065>..Server: Linksys/SPA962-5.1.18(SC)..Content-Length: 209..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER..Supported: replaces..Content-Type: application/sdp....v=0..o=- 317989 317989 IN IP4 192.168.1.124..s=-..c=IN IP4 147.202.001.001..t=0 0..m=audio 35984 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 58.28.001.001:5065 -> 147.202.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.124:5065;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 70..Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Record-Route: <sip:147.202.001.001;lr=on;ftag=9f9da889431cd5afi5>..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKac76.c88550f.0..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 69..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 58.28.001.001:5060 -> 147.202.001.001:5060SIP/2.0 200 OK..Via: SIP/2.0/UDP 147.202.001.001;branch=z9hG4bKac76.c88550f.0..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..CSeq: 101 BYE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@192.168.1.102>..Record-Route: <sip:147.202.001.001;lr=on;ftag=9f9da889431cd5afi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..CSeq: 101 BYE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Record-Route: <sip:147.202.001.001;lr=on;ftag=9f9da889431cd5afi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... U 58.28.001.001:5065 -> 147.202.001.001:5060BYE sip:44556648@58.28.001.001:5060 SIP/2.0..Via: SIP/2.0/UDP 192.168.1.124:5065;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..CSeq: 101 BYE..Max-Forwards: 70..Route: <sip:147.202.001.001:5060;nat=yes;ftag=3D7BF99A-F3B3ACE5;lr=on>..User-Agent: Linksys/SPA962-5.1.18(SC)..Content-Length: 0.... U 147.202.001.001:5060 -> 58.28.001.001:5065SIP/2.0 200 OK..Via: SIP/2.0/UDP 192.168.1.124:5065;received=58.28.001.001;branch=z9hG4bK-6829d146..From: <sip:44556644@domain.com;user=phone>;tag=9f9da889431cd5afi5..To: "CSB" <sip:44556648@domain.com>;tag=3D7BF99A-F3B3ACE5..CSeq: 101 BYE..Call-ID: 26e8c161-7e674928-90cba56b@192.168.1.102..Contact: <sip:44556648@58.28.001.001:5060>..Record-Route: <sip:147.202.001.001;lr=on;ftag=9f9da889431cd5afi5>..User-Agent: PolycomSoundPointIP-SPIP_320-UA/2.1.1.0037..Content-Length: 0.... ************************** iptables config $IPTABLES -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT $IPTABLES -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT $IPTABLES -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT # # Rule 0 (tun0,tun1,tun2) # echo "Rule 0 (tun0,tun1,tun2)" # # # $IPTABLES -N In_RULE_0 $IPTABLES -A INPUT -i tun0 -m state --state NEW -j In_RULE_0 $IPTABLES -A INPUT -i tun1 -m state --state NEW -j In_RULE_0 $IPTABLES -A INPUT -i tun2 -m state --state NEW -j In_RULE_0 $IPTABLES -A FORWARD -i tun0 -m state --state NEW -j In_RULE_0 $IPTABLES -A FORWARD -i tun1 -m state --state NEW -j In_RULE_0 $IPTABLES -A FORWARD -i tun2 -m state --state NEW -j In_RULE_0 $IPTABLES -A In_RULE_0 -j LOG --log-level warning --log-prefix "RULE 0 -- ACCEPT " $IPTABLES -A In_RULE_0 -j ACCEPT $IPTABLES -N Out_RULE_0 $IPTABLES -A OUTPUT -o tun0 -m state --state NEW -j Out_RULE_0 $IPTABLES -A OUTPUT -o tun1 -m state --state NEW -j Out_RULE_0 $IPTABLES -A OUTPUT -o tun2 -m state --state NEW -j Out_RULE_0 $IPTABLES -A FORWARD -o tun0 -m state --state NEW -j Out_RULE_0 $IPTABLES -A FORWARD -o tun1 -m state --state NEW -j Out_RULE_0 $IPTABLES -A FORWARD -o tun2 -m state --state NEW -j Out_RULE_0 $IPTABLES -A Out_RULE_0 -j LOG --log-level warning --log-prefix "RULE 0 -- ACCEPT " $IPTABLES -A Out_RULE_0 -j ACCEPT $IPTABLES -A Out_RULE_0 -j ACCEPT # # Rule 1 (lo) # echo "Rule 1 (lo)" # # # $IPTABLES -N In_RULE_1 $IPTABLES -A INPUT -i lo -p icmp -m icmp --icmp-type any -m state --state NEW -j In_RULE_1 $IPTABLES -A INPUT -i lo -p tcp -m tcp -m multiport --dports 25060,8008,25,443,80,22,3306,5060 -m state --state NEW -j In_RULE_1 #$IPTABLES -A INPUT -i lo -p udp -m udp -m multiport --dports 5060,1813 -m state --state NEW -j In_RULE_1 $IPTABLES -A INPUT -i lo -p udp -m udp -m multiport --dports 1:55000 -m state --state NEW -j In_RULE_1 $IPTABLES -A In_RULE_1 -j LOG --log-level warning --log-prefix "RULE 1 -- ACCEPT " $IPTABLES -A In_RULE_1 -j ACCEPT $IPTABLES -N Out_RULE_1 $IPTABLES -A OUTPUT -o lo -p icmp -m icmp --icmp-type any -m state --state NEW -j Out_RULE_1 $IPTABLES -A OUTPUT -o lo -p tcp -m tcp -m multiport --dports 25060,8008,25,443,80,22,3306,5060 -m state --state NEW -j Out_RULE_1 #$IPTABLES -A OUTPUT -o lo -p udp -m udp -m multiport --dports 5060,1813 -m state --state NEW -j Out_RULE_1 $IPTABLES -A OUTPUT -o lo -p udp -m udp -m multiport --dports 1:55000 -m state --state NEW -j Out_RULE_1 $IPTABLES -A Out_RULE_1 -j LOG --log-level warning --log-prefix "RULE 1 -- ACCEPT " $IPTABLES -A Out_RULE_1 -j ACCEPT # # Rule 2 (eth0) # echo "Rule 2 (eth0)" # # # $IPTABLES -N Out_RULE_2 $IPTABLES -A OUTPUT -o eth0 -d 10.8.1.1 -m state --state NEW -j Out_RULE_2 $IPTABLES -A FORWARD -o eth0 -d 10.8.1.1 -m state --state NEW -j Out_RULE_2 $IPTABLES -A Out_RULE_2 -j LOG --log-level warning --log-prefix "RULE 2 -- ACCEPT " $IPTABLES -A Out_RULE_2 -j ACCEPT # # Rule 3 (eth0) # echo "Rule 3 (eth0)" # # ping test for nagios # $IPTABLES -N Cid485B0E561900.0 $IPTABLES -A INPUT -i eth0 -d 147.202.001.001 -m state --state NEW -j Cid485B0E561900.0 $IPTABLES -N Cid485B0E561900.1 $IPTABLES -A Cid485B0E561900.0 -p icmp -m icmp --icmp-type any -j Cid485B0E561900.1 $IPTABLES -A Cid485B0E561900.0 -p tcp -m tcp -m multiport --dports 25,3306 -j Cid485B0E561900.1 $IPTABLES -N In_RULE_3 $IPTABLES -A Cid485B0E561900.1 -s 203.89.001.001 -j In_RULE_3 $IPTABLES -A Cid485B0E561900.1 -s 58.28.001.001 -j In_RULE_3 $IPTABLES -A Cid485B0E561900.1 -s 64.38.001.001 -j In_RULE_3 $IPTABLES -A In_RULE_3 -j LOG --log-level warning --log-prefix "RULE 3 -- ACCEPT " $IPTABLES -A In_RULE_3 -j ACCEPT # echo "Rule 4 (eth0)" # # ping test for nagios # $IPTABLES -N Cid485B0E6A1900.0 $IPTABLES -A OUTPUT -o eth0 -s 147.202.001.001 -m state --state NEW -j Cid485B0E6A1900.0 $IPTABLES -N Cid485B0E6A1900.1 $IPTABLES -A Cid485B0E6A1900.0 -p icmp -m icmp --icmp-type any -j Cid485B0E6A1900.1 $IPTABLES -A Cid485B0E6A1900.0 -p tcp -m tcp -m multiport --dports 25,3306 -j Cid485B0E6A1900.1 $IPTABLES -N Out_RULE_4 $IPTABLES -A Cid485B0E6A1900.1 -d 203.89.001.001 -j Out_RULE_4 $IPTABLES -A Cid485B0E6A1900.1 -d 58.28.001.001 -j Out_RULE_4 $IPTABLES -A Cid485B0E6A1900.1 -d 64.38.001.001 -j Out_RULE_4 $IPTABLES -A Out_RULE_4 -j LOG --log-level warning --log-prefix "RULE 4 -- ACCEPT " $IPTABLES -A Out_RULE_4 -j ACCEPT # # Rule 5 (eth0) # echo "Rule 5 (eth0)" # # # $IPTABLES -N In_RULE_5 $IPTABLES -A INPUT -i eth0 -p tcp -m tcp -m multiport -d 147.202.001.001 --dports 5060,22,443,80,53,25060,8008 -m state --state NEW -j In_RULE_5 #$IPTABLES -A INPUT -i eth0 -p udp -m udp -d 147.202.001.001 --dport 10000:20000 -m state --state NEW -j In_RULE_5 #$IPTABLES -A INPUT -i eth0 -p udp -m udp -d 147.202.001.001 --dport 35000:36000 -m state --state NEW -j In_RULE_5 #$IPTABLES -A INPUT -i eth0 -p udp -m udp -m multiport -d 147.202.001.001 --dports 1194,5065,5060,53,10000:20000,35000:36000 -m state --state NEW -j In_RULE_5 $IPTABLES -A INPUT -i eth0 -p udp -m udp -m multiport --dports 1:55000 -m state --state NEW -j In_RULE_5 $IPTABLES -A In_RULE_5 -j LOG --log-level warning --log-prefix "RULE 5 -- ACCEPT " $IPTABLES -A In_RULE_5 -j ACCEPT # # Rule 6 (eth0) # echo "Rule 6 (eth0)" # # # $IPTABLES -N Out_RULE_6 $IPTABLES -A OUTPUT -o eth0 -p tcp -m tcp -m multiport -s 147.202.001.001 --dports 22,53,80,443,5060,8008,25060,25 -m state --state NEW -j Out_RULE_6 #$IPTABLES -A OUTPUT -o eth0 -p udp -m udp -s 147.202.001.001 --dport 10000:20000 -m state --state NEW -j Out_RULE_6 #$IPTABLES -A OUTPUT -o eth0 -p udp -m udp -s 147.202.001.001 --dport 35000:36000 -m state --state NEW -j Out_RULE_6 #$IPTABLES -A OUTPUT -o eth0 -p udp -m udp -m multiport -s 147.202.001.001 --dports 53,1194,5060,5065,1813,123,10000:20000,35000:36000 -m state --state NEW -j Out_RULE_6 $IPTABLES -A OUTPUT -o eth0 -p udp -m udp -m multiport --dports 1:55000 -m state --state NEW -j Out_RULE_6 $IPTABLES -A Out_RULE_6 -j LOG --log-level warning --log-prefix "RULE 6 -- ACCEPT " $IPTABLES -A Out_RULE_6 -j ACCEPT # # Rule 7 (global) # echo "Rule 7 (global)" # # # $IPTABLES -N RULE_7 $IPTABLES -A OUTPUT -j RULE_7 $IPTABLES -A INPUT -j RULE_7 $IPTABLES -A FORWARD -j RULE_7 $IPTABLES -A RULE_7 -j LOG --log-level warning --log-prefix "RULE 7 -- DENY " $IPTABLES -A RULE_7 -j DROP # #

1 0

[Serusers] use_dns_cache and call forwarding
by caio 24 Jul '08

24 Jul '08

Hi guys, I have a problem with call forwarding (on busy or not answer).., the call fall into the failure_route(1) block, and AVP checking and pushto does its job. Here a snipped of code of failure_route(1) (flag 27 means call fwd if no answer): if (isflagset(27) && t_check_status("408")) { # if fwd no answer is set and reply msg is 408 if (avp_pushto("$ruri", "s:fwdnoanswer")) { avp_delete("s:fwdnoanswer"); resetflag(27); avp_print(); log(1, "LOG: --> appending new branch..."); if (!append_branch()){ t_reply("500", "Too many branches?!"); drop; } log(1, "LOG: --> Calling route_6..."); route(6); break; Route(6) finally calls route(1), where t_relay is called. But have a dns failure..and the call never is forwarded. == ser.log == DEBUG: mk_proxy: doing DNS lookup... get_record: lookup(_sip._udp.wsa.lab, 33) failed_ sip_resolvehost: no SRV record found for wsa.lab, trying 'normal' lookup..._ check_via_address(190.244.33.5, 190.244.33.5, 0)_ ERROR: udp_send: sendto(sock,0x2ab32599c720,910,0,0x2ab325999e68,16): Operation not permitted(1)_ msg_send: ERROR: udp_send failed_ ERROR: t_forward_nonack: sending request failed_ DEBUG: add_to_tail_of_timer[4]: 0x2ab325999e80_ DEBUG: add_to_tail_of_timer[0]: 0x2ab325999ea0_ ERROR: w_t_relay (failure mode): forwarding failed_ A question regarding this trouble.....Can I disable use_dns_cache ? SER version is 0.9.7. What do you recommend? If you need my ser.cfg I can paste it... Thanks.. -- caio

2 1

Re: [OpenSER-Users] CDRTool with OpenSER
by Rana Dhekial 24 Jul '08

24 Jul '08

Hi Dan, Please find output of 'dkpg -l 'php4-*'. Looks like php4-mysql is installed. openser:~# dpkg -l 'php4-*'Desired=Unknown/Install/Remove/Purge/Hold| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)||/ Name Version Description+++-==============-==============-============================================ii php4-cgi 4.4.4-8+etch6 server-side, HTML-embedded scripting languagun php4-cli <none> (no description available)ii php4-common 4.4.4-8+etch6 Common files for packages built from the phpun php4-curl <none> (no description available)ii php4-dev 4.4.4-8+etch6 Files for PHP4 module developmentun php4-memcache <none> (no description available)ii php4-mysql 4.4.4-8+etch6 MySQL module for php4ii php4-pear 4.4.4-8+etch6 PHP Extension and Application Repository (trun php4-pgsql <none> (no description available)/etc/php4/apache2/php.ini has the following lines.. extension=mysql.so Please let me know any additional config required. thanks, Rana Date: Thu, 24 Jul 2008 07:02:42 +0200From: danb(a)sms4sip.comTo: dhekial(a)msn.comSubject: Re: [OpenSER-Users] CDRTool with OpenSERCC: users(a)lists.openser.org Hi Rana,you need to have php4-mysql installed and loaded in your php code.DanB On Thu, Jul 24, 2008 at 3:00 AM, Rana Dhekial <dhekial(a)msn.com> wrote: We are trying to install cdrtool on the same machine where OpenSER ( 1.2.2 ) is running. We get the following error message when trying to access the page: http://<ipaddress>/CDRToolFatal error: Call to undefined function: mysql_pconnect() in /var/www/CDRTool/phplib/db_mysql.inc on line 73MySQL version is 5.0.32, Apache version is 2.2.3, php version is 4.please let us know if there is anything we can do to fix this problem. thanks, Rana Use video conversation to talk face-to-face with Windows Live Messenger. Get started._______________________________________________Users mailing listUsers@lists.openser.orghttp://lists.openser.org/cgi-bin/mailman/listinfo/users _________________________________________________________________ Time for vacation? WIN what you need- enter now! http://www.gowindowslive.com/summergiveaway/?ocid=tag_jlyhm

2 1

← Newer
1
...
5
6
7
8
9
10
11
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2008