Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

LanScape VOIP Media Engine™ - Pre-Sales Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Subject Topic: VOiP Integration Question Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
TJMcMeley
Intermediate
Intermediate


Joined: April 19 2007
Location: United States
Posts: 20
Posted: April 19 2007 at 3:05am | IP Logged Quote TJMcMeley
Hello,

I am very excited to find your product. To tell the truth, VoIP integration so far has been an R&D nightmare for my team. While I’m primarily a .Net/VB/TSQL/Messaging guy, I like to think I am always open to learn. But support from other VoIP third party vendors has been less than stellar.

I have an add-on request for our existing automotive production management system to send canned audio messages thru VoIP speakers in their break rooms, warning tradesmen when problems are occurring in the lines.

I have sent a request for a trial license, but I would greatly appreciate what information you might be able to provide.
  • These devices supports SIP (RFC 3261), or RTP streams on IP addresses and ports, using the uLaw (g.711) codec at 20 ms

  • We can connect to the device for testing using RTP and JMStudio (The Sun Java product) with an IP and port, but we cannot get the codec to function. Most likely setup issues with the codec from what we can deduce.

  • If we can avoid adding a SIP Server, to reduce complexity, that would be best, but I am not against configuring your SIP Server product if we must.

  • The customer requires the code be based in VB.Net, but if we have to call C# or C++ we will. However, it will be a thorny issue to pass their IT department, so if we can stay in VB.Net our life would be much easier.


Other vendors have been either cagey in their capabilities, or completely missing in action. From your documentation so far, you look like an excellent fit and we’re looking forward to better success.

Thank you
Back to Top View TJMcMeley's Profile Search for other posts by TJMcMeley
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 19 2007 at 11:58am | IP Logged Quote support
Hi TJ,

Thanks for posting your questions to this support forum. Your VOIP application requirements appear to be pretty straight forward.


Item 1:
We have CyberData VoIP ceiling speakers.

<<< Support
Looks like a cool device. We reviewed the specs for this device - Operation Manual (Firmware 3.00). Seeing that it has been inter-op tested with Asterisk, it should also have no problem functioning with an application that integrates the LanScape VOIP Media Engine. We would have to actually verify this however.


Item 2:
These devices supports SIP (RFC 3261), or RTP streams on IP addresses and ports, using the uLaw (g.711) codec at 20 ms.

<<< Support
Yes. Good.


Item 3:
If we can avoid adding a SIP Server, to reduce complexity, that would be best, but I am not against configuring your SIP Server product if we must.

<<< Support
If your VOIP application and speaker endpoints are all located in the same physical subnet (this assumes no NAT router or firewall issues), then you will not need to deploy server elements. Your VOIP app that uses the media engine can directly call the speaker endpoints.

If your VOIP deployment is in a network environment that consists of speakers being in other subnets and/or behind NAT routers or firewalls relative to your VOIP application, then a SIP + RTP media proxy server deployment is a good idea. If you do not deploy a “server element”, then you will be faced with the nightmare of making sure the network gets configured properly and stays that way (setting port forwarding in NAT routers and appropriate rules in the firewalls). It’s usually a network headache using this approach. The preferred way is to deploy a single LanScape Centrex SIP proxy + LanScape VOIP Media Proxy in the network environment that is globally accessible to all VOIP endpoints. This will remove all these issues and maintenance hassles regarding special NAT and firewall configurations. No special network configuration is required.


Item 4:
The customer requires the code be based in VB.Net, but if we have to call C# or C++ we will. However, it will be a thorny issue to pass their IT department, so if we can stay in VB.Net our life would be much easier.

<<< Support
VB.Net is no problem. We are ready to release the next version of the media engine that supports all .NET languages and managed code. If you decide to purchase before we perform the final release, we will get you the official pre-release version of the product.


Actually, we would like to see if we could call one of your CyberData speakers from here. If you want, configure one of the speakers at your location so that we have access to its IP address and port and we will attempt test calls to check out inter-op. We will play some nice muzak for you when the call connects. Let us know via email if you want to do this. We will post a SIP log of the call setup and termination.


Repost as needed,


Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
TJMcMeley
Intermediate
Intermediate


Joined: April 19 2007
Location: United States
Posts: 20
Posted: April 19 2007 at 10:30pm | IP Logged Quote TJMcMeley
Hello,

Thank you for the generous offer; we will definitely take you up on it! I need to arrange for a static IP and resources. I am supposed leave to be on site next week, so I need to get everyone on board and will reply back with the necessary information.

Thanks,

TJ
Back to Top View TJMcMeley's Profile Search for other posts by TJMcMeley
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 24 2007 at 3:29pm | IP Logged Quote support
Hi TJ,

We performed our initial inter-op testing with the CyberData VOIP speaker that you allowed us to access. Those are pretty cool devices. We like them.

Here is what we did:

Performed direct communications using the VOIP Media Engine:
We used a test soft phone we have here that uses the VOIP Media Engine. We set up the speakers SIP configuration so it acts as a stand alone user agent – no registration to a proxy, etc.

The VOIP Media Engine soft phone was also configured in a stand alone manner. We then called the CyberData speaker directly using aLaw and then uLaw. Calls connected as expected.

We also tested to see what would happen when we tried to establish call sessions using codecs that are unsupported by the CyberData speaker. The speaker returned a SIP error response “unsupported media type” as expected.

So in a nutshell, direct calling the CyberData speaker using the LanScape VOIP Media Engine worked with no problems.


Call setup using LanScape Centrex SIP proxy and VOIP Media proxy:
In this test scenario, we configured the CyberData speaker to register with a LanScape Centrex SIP proxy we have here in our lab. We also configured a LanScape VOIP Media Proxy server into the mix to handle NAT router issues. Both of these servers were on our own private network behind our outermost NAT router.

Speaker registering – no authentication:
We tested the CyberData speaker’s ability to register with the proxy – not using authentication. The test passed and the speaker registered no problems.

Speaker registering – with authentication:
We then activated authentication on the Centrex SIP proxy. We configured the speaker with appropriate authentication information and rebooted it. The CyberData speaker registered with authentication no problems.

At this point the CyberData speaker is part of the proxy’s VOIP domain. We used the VOIP Media Engine soft phone to call the speaker. The call setup went as expected and we streamed media to the speaker for a while. We did this using uLaw and then aLaw RTP payloads.

Call hold and un-hold operations:
We tested the ability of the speaker to handle call hold and un-hold requests from the media engine. This worked as expected.

So in a “second” nutshell, calling the CyberData speaker using the LanScape VOIP Media Engine and the LanScape SIP and RTP proxy products worked with no problems.



Here are a few of the SIP logs we gathered while performing the tests:

Note: The global IP address of your speaker and our WAN IP address has been changed for security purposes.


Proxy SIP Log - Register with authentication:

Code:

************* Log Opened (Apr 24 12:43:56) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
REGISTER sip:122.73.79.80:5060 SIP/2.0
Via: SIP/2.0/UDP 166.141.99.29:5060;rport;branch=z9hG4bK1909650913
From: <sip:205@122.73.79.80>;tag=1883799469
To: <sip:205@122.73.79.80>
Call-ID: 416756883@166.141.99.29
CSeq: 1 REGISTER
Contact: <sip:205@166.141.99.29:5060>
Max-Forwards: 5
User-Agent: SipSpkr v2.01
Expires: 3600
Content-Length: 0




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 166.141.99.29:5060;rport=5060;branch=z9hG4bK1909650913;recei ved=166.141.99.29
From: <sip:205@122.73.79.80>;tag=1883799469
To: <sip:205@122.73.79.80>
Call-ID: 416756883@166.141.99.29
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="ps", nonce="1c6aed7d938a9492aeb3a3e57c65d086", opaque="efdfd5216a53a3e446c27633b8fef040"
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
REGISTER sip:122.73.79.80:5060 SIP/2.0
Via: SIP/2.0/UDP 166.141.99.29:5060;rport;branch=z9hG4bK877491740
From: <sip:205@122.73.79.80>;tag=1883799469
To: <sip:205@122.73.79.80>
Call-ID: 416756883@166.141.99.29
CSeq: 2 REGISTER
Contact: <sip:205@166.141.99.29:5060>
Authorization: Digest username="user", realm="ps", nonce="1c6aed7d938a9492aeb3a3e57c65d086", uri="sip:122.73.79.80:5060", response="6047c8ba5878b88029d4e452a0ebe162", algorithm=MD5, opaque="efdfd5216a53a3e446c27633b8fef040"
Max-Forwards: 5
User-Agent: SipSpkr v2.01
Expires: 3600
Content-Length: 0




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 166.141.99.29:5060;rport=5060;branch=z9hG4bK877491740;receiv ed=166.141.99.29
From: <sip:205@122.73.79.80>;tag=1883799469
To: <sip:205@122.73.79.80>;tag=41
Call-ID: 416756883@166.141.99.29
CSeq: 2 REGISTER
Contact: <sip:205@166.141.99.29:5060>;expires=3600
Expires: 3600
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0


************* Log Closed (Apr 24 12:46:22) *************




Media Engine SIP Log, ulaw - direct - no proxy:

Code:

************* Log Opened (Apr 24 11:55:08) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#16, 95125 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011cc9ab
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>
Contact: <sip:333@192.168.1.2:5096>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18640625 18640625 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16120 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#24, 95422 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011cc9ab;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#25, 47 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011cc9ab;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#26, 187 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011cc9ab;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#27, 31 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011cc9ab;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#17, 437 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011cc9ab
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893816 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#18, 18688 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011d0a76
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Contact: <sip:333@192.168.1.2:5096>
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893817 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 217
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18659750 18659750 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 16120 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#28, 18875 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d0a76;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893817 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#29, 360 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d0a76;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893817 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#19, 546 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011d0a76
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893817 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#20, 22969 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011d3b98
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Contact: <sip:333@192.168.1.2:5096>
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18683265 18683265 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16120 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#30, 23172 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d3b98;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#31, 15 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d3b98;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#32, 188 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d3b98;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#33, 31 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d3b98;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#21, 438 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011d3b98
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893818 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#22, 12406 Ms, To: 166.141.99.29:5060) >>>>
BYE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011d6f72
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-Id: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893819 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#34, 12625 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011d6f72;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11c7b12;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=635847020
Call-ID: 4c50fc8f-c1ce-4a77-911a-9babece3ee97-000033a0@192.168.1.2
CSeq: 1893819 BYE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0


************* Log Closed (Apr 24 11:56:15) *************




Media Engine SIP Log, alaw - direct - no proxy:

Code:

************* Log Opened (Apr 24 11:57:22) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#23, 77594 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011e927f
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>
Contact: <sip:333@192.168.1.2:5096>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18773703 18773703 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16002 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#35, 77578 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011e927f;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#36, 0 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011e927f;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#37, 188 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011e927f;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#38, 62 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011e927f;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#24, 453 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011e927f
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016051 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#25, 14312 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011edcf2
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Contact: <sip:333@192.168.1.2:5096>
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016052 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 217
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18788468 18788468 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 16002 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#39, 14500 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011edcf2;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016052 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#40, 188 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011edcf2;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016052 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#26, 360 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011edcf2
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016052 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#27, 39140 Ms, To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011f5643
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Contact: <sip:333@192.168.1.2:5096>
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 18827968 18827968 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 16002 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#41, 39312 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011f5643;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#42, 47 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011f5643;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#43, 172 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011f5643;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#44, 94 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011f5643;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#28, 485 Ms, To: 166.141.99.29:5060) >>>>
ACK sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;received=122.73.79.80;rport=5096;branch=z9h G4bK011f5643
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016053 ACK
Max-Forwards: 70
Route: <sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#29, 11578 Ms, To: 166.141.99.29:5060) >>>>
BYE sip:205@166.141.99.29 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK011f99b3
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-Id: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016054 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#45, 11750 Ms, From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK011f99b3;received= 122.73.79.80
From: "LanScape Phone 333" <sip:333@192.168.1.2:5096>;tag=11ed30a;x-UaId=xxxxx-yy yy-zzzzzz
To: <sip:205@166.141.99.29>;tag=963236072
Call-ID: a4ffa278-7f2e-4c48-8390-1bdb87154602-000033a0@192.168.1.2
CSeq: 2016054 BYE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0




************* Log Closed (Apr 24 11:58:34) *************



Media Engine calling via proxy. This is the Proxy SIP Log, ulaw codec:

Code:

************* Log Opened (Apr 24 12:39:05) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0145224b
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e5f6;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507282 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21279453 21279453 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145224b;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e5f6;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507282 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145224b;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e5f6;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507282 INVITE
Proxy-Authenticate: Digest realm="ps", nonce="07725a615e77496c8f17ca3e527d0b93", opaque="b01b000ac835a9d7830afa09af12849c"
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0145224b
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e5f6;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507282 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0145226a
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Contact: <sip:333@192.168.1.2:6060>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="07725a615e77496c8f17ca3e527d0b93",opaqu e="b01b000ac835a9d7830afa09af12849c",realm="ps",response="b5 8493a09848a3ac8b116875415afad0",uri="sip:205@ps",username="g uest"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21279484 21279484 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29:5060 SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf3d021f1a1e5c6b5f342dc68dd5b e2e27.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:333@122.73.79.80:6060>;x-inst="VGVzdCBDYWxsIERhdG EgZnJvbSB0aGUgVlBob25lIGFwcC4="
max-forwards: 69
organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   221

v=0
o=333 21279484 21279484 IN IP4 122.73.79.80
s=LanScape
c=IN IP4 122.73.79.80
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf3d021f1a1e5c6b5f342dc68dd5b e2e27.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf3d021f1a1e5c6b5f342dc68dd5b e2e27.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 101 Dialog Establishement
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf3d021f1a1e5c6b5f342dc68dd5b e2e27.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf3d021f1a1e5c6b5f342dc68dd5b e2e27.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:122.73.79.80:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145226a;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 INVITE
Contact: <sip:205@166.141.99.29:5060>
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   228

v=0
o=cyberdata 0 0 IN IP4 192.168.1.2
s=conversation
c=IN IP4 192.168.1.2
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0145226a
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKl3d021f1a1e5c6b5f342dc68dd5b e2e27
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0145226a
Route: <sip:205@166.141.99.29>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507313 ACK
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK014528ab
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Contact: <sip:333@192.168.1.2:6060>
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507314 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 217
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21288031 21288031 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK014528ab;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507314 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK014528ab;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507314 INVITE
Proxy-Authenticate: Digest realm="ps", nonce="07725a615e77496c8f17ca3e527d0b93", opaque="697e11df0be66a2851e30fd8a1a9c81a"
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK014528ab
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507314 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK01453834
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Contact: <sip:333@192.168.1.2:6060>
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="07725a615e77496c8f17ca3e527d0b93",opaqu e="697e11df0be66a2851e30fd8a1a9c81a",realm="ps",response="b5 8493a09848a3ac8b116875415afad0",uri="sip:205@ps",username="g uest"
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 217
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21288093 21288093 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01453834;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29:5060 SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf09cff23fbe8c92d1ecbcb39ac93 2c4e6.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01453834;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
Route: <sip:205@166.141.99.29>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Contact: <sip:333@122.73.79.80:6060>
max-forwards: 69
organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   217

v=0
o=333 21288093 21288093 IN IP4 122.73.79.80
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf09cff23fbe8c92d1ecbcb39ac93 2c4e6.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01453834;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf09cff23fbe8c92d1ecbcb39ac93 2c4e6.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01453834;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01453834;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 INVITE
Contact: <sip:205@166.141.99.29:5060>
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   228

v=0
o=cyberdata 0 0 IN IP4 192.168.1.2
s=conversation
c=IN IP4 192.168.1.2
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK01453834
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKl09cff23fbe8c92d1ecbcb39ac93 2c4e6
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK01453834
Route: <sip:205@166.141.99.29>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507315 ACK
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0144eb87
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Contact: <sip:333@192.168.1.2:6060>
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507316 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21293687 21293687 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0144eb87;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507316 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0144eb87;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507316 INVITE
Proxy-Authenticate: Digest realm="ps", nonce="07725a615e77496c8f17ca3e527d0b93", opaque="bd5396128125e96d2f95808292348ab5"
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0144eb87
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507316 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
INVITE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0145626b
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Contact: <sip:333@192.168.1.2:6060>
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="07725a615e77496c8f17ca3e527d0b93",opaqu e="bd5396128125e96d2f95808292348ab5",realm="ps",response="b5 8493a09848a3ac8b116875415afad0",uri="sip:205@ps",username="g uest"
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=333 21293734 21293734 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 20002 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145626b;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
INVITE sip:205@166.141.99.29:5060 SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKfb8c1b9f526f964ddd01e0f3b8ea e1c8a.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145626b;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
Route: <sip:205@166.141.99.29>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Contact: <sip:333@122.73.79.80:6060>
max-forwards: 69
organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   221

v=0
o=333 21293734 21293734 IN IP4 122.73.79.80
s=LanScape
c=IN IP4 122.73.79.80
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKfb8c1b9f526f964ddd01e0f3b8ea e1c8a.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145626b;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKfb8c1b9f526f964ddd01e0f3b8ea e1c8a.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145626b;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Contact: <sip:205@166.141.99.29:5060>
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   231

v=0
o=cyberdata 0 0 IN IP4 166.141.99.29
s=conversation
c=IN IP4 166.141.99.29
t=0 0
m=audio 10500 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0145626b;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 INVITE
Contact: <sip:205@166.141.99.29:5060>
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Type: application/sdp
Content-Length:   228

v=0
o=cyberdata 0 0 IN IP4 192.168.1.2
s=conversation
c=IN IP4 192.168.1.2
t=0 0
m=audio 16001 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20




<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0145626b
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 ACK
Max-Forwards: 70
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
ACK sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKlb8c1b9f526f964ddd01e0f3b8ea e1c8a
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK0145626b
Route: <sip:205@166.141.99.29>
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507317 ACK
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
BYE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK01454f00
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507318 BYE
Max-Forwards: 70
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01454f00;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507318 BYE
Proxy-Authenticate: Digest realm="ps", nonce="07725a615e77496c8f17ca3e527d0b93", opaque="606a74fcad1e7d9906bfe21198f48b55"
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:6060) <<<<
BYE sip:205@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK01452440
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-Id: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507319 BYE
Max-Forwards: 70
Proxy-Authorization: Digest algorithm=md5,nonce="07725a615e77496c8f17ca3e527d0b93",opaqu e="606a74fcad1e7d9906bfe21198f48b55",realm="ps",response="f4 57de8c5fb00a2cb77611348b6b9531",uri="sip:205@ps",username="g uest"
Route: <sip:192.168.1.2;lr>,<sip:205@166.141.99.29>
User-Agent: LanScape VOIP Media Engine/5.12.3.21 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 166.141.99.29:5060) >>>>
BYE sip:205@166.141.99.29:5060 SIP/2.0
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf764d0ca5b579edd4c18b811ed5e 1442c.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01452440;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507319 BYE
max-forwards: 69
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Content-Length: 0





<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 166.141.99.29:5060) <<<<
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/UDP 122.73.79.80:5060;branch=z9hG4bKf764d0ca5b579edd4c18b811ed5e 1442c.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01452440;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507319 BYE
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0





>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:6060) >>>>
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK01452440;received= 192.168.1.2
From: "(3-3_3.3!3~3*3)aa   a`1234567890-=~!@#$%^&*( )_+qwertyuiop[]|}{asdfghjkl;':zxcvbnm,./?/*-+zzz" <sip:333@ps>;tag=144e615;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:205@ps>;tag=16789239
Call-ID: 0a6a7c05-2109-455d-abab-49ea5cdd41ab-000000d4@192.168.1.2
CSeq: 4507319 BYE
Server: LanScape Centrex Proxy/3.42.1.8 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, MESSAGE, INFO, REFER, UPDATE
Content-Length: 0


************* Log Closed (Apr 24 12:39:40) *************



Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights