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™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: Problem Registering Mitel 3300 IP PBX Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 07 2007 at 6:21am | IP Logged Quote Jalal
Hi

We have an Authentication problem with Mitel 3300 IP PBX. We have tested with v5.12.3.27.

Following is our software log connecting to this IP PBX.
Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, 0 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ceff4
From: <sip:9090@192.168.0.241>;tag=41c8bde
To: <sip:9090@192.168.0.241>
Call-Id: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883799 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.91:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ceff4
From: <sip:9090@192.168.0.241>;tag=41c8bde
To: <sip:9090@192.168.0.241>;tag=MitelICP_2593664896-56863 892
Call-ID: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883799 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ceff4
WWW-Authenticate: Digest realm="XIRA CORP",nonce="__!;e6oHNGj8=E_$!GJAgsam],Oa9}Vw1}]'b%}*`3/S> ;D3gYY;X#o8p<SG2Ep1W",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=41c8bde
To: <sip:9090@192.168.0.241>;tag=MitelICP_2593664896-56863 892
Call-ID: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883799 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, 47 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ccf74
From: <sip:9090@192.168.0.241>;tag=41cd4b0
To: <sip:9090@192.168.0.241>
Call-Id: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883800 REGISTER
Authorization: Digest algorithm=md5, cnonce="001c940e", nc="00000001", qop="auth", realm="XIRA CORP", response="9919b50fd677e771e7684651c5bdaea2", uri="sip:192.168.0.241", username="9090"
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.91:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.27 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, 31 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ccf74
From: <sip:9090@192.168.0.241>;tag=41cd4b0
To: <sip:9090@192.168.0.241>;tag=MitelICP_2593694896-56863 893
Call-ID: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883800 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK041ccf74
From: <sip:9090@192.168.0.241>;tag=41cd4b0
To: <sip:9090@192.168.0.241>;tag=MitelICP_2593694896-56863 893
Call-ID: ce305bfa-b717-45e2-84e4-7115a94e5c2d-00001678@192.168.0.91
CSeq: 1883800 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0


Mitel sends us SIP 403 Forbidden message. But we are sure we have set correct username and password because the same user name and password works on Phoner Free softphone. Following is ethreal saved log of Phoner connection to Mitel.

Code:

REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978200c026a1 a11e
From: Daria <sip:9090@192.168.0.241>;tag=24597
To: <sip:9090@192.168.0.241>
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 1 REGISTER
Contact: <sip:9090@192.168.0.91:5063>
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 900
Content-Length: 0



Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978200c026a1 a11e
From: Daria <sip:9090@192.168.0.241>;tag=24597
To: <sip:9090@192.168.0.241>;tag=MitelICP_3012104896-56863 911
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 1 REGISTER
Content-Length: 0

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978200c026a1 a11e
WWW-Authenticate: Digest realm="XIRA CORP",nonce=".{u9Mr~z_/%?zEL<Y^cY3HQY]|[Ca~(W;Inz>Bqz1 _gNN&{8`e&5Pk+Z#2snXB(h",algorithm=MD5,qop="auth"
From: Daria <sip:9090@192.168.0.241>;tag=24597
To: <sip:9090@192.168.0.241>;tag=MitelICP_3012104896-56863 911
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 1 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0

REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978300c026a1 a11e
From: Daria <sip:9090@192.168.0.241>;tag=6964
To: <sip:9090@192.168.0.241>
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 2 REGISTER
Contact: <sip:9090@192.168.0.91:5063>
Authorization: Digest username="9090", realm="XIRA CORP", nonce=".{u9Mr~z_/%?zEL<Y^cY3HQY]|[Ca~(W;Inz>Bqz1_gNN&{ 8`e&5Pk+Z#2snXB(h", uri="sip:192.168.0.241", response="1c5e0dfb9a7b146550d1d4da9ddf76d5", algorithm=MD5, cnonce="234abcc436e2667097e7fe6eia53e8dd", qop=auth, nc=00000001
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 900
Content-Length: 0

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978300c026a1 a11e
From: Daria <sip:9090@192.168.0.241>;tag=6964
To: <sip:9090@192.168.0.241>;tag=MitelICP_3012134896-56863 912
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 2 REGISTER
Content-Length: 0

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.91:5063;branch=z9hG4bK80fc6682dffadb11978300c026a1 a11e
From: Daria <sip:9090@192.168.0.241>;tag=6964
To: <sip:9090@192.168.0.241>;tag=MitelICP_3012134896-56863 912
Call-ID: 0066CE81-DFFA-DB11-9782-00C026A1A11E@192.168.0.91
CSeq: 2 REGISTER
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Contact: <sip:9090@192.168.0.91:5063>;expires=900
Expires: 0
Content-Length: 0


Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 07 2007 at 3:32pm | IP Logged Quote support
Hi Jalal,

Thanks for this SIP log and this post.

I bet you anything there is a parsing error associated with the “nonce” value coming back from the “401 Unauthorized” SIP response from the Mitel PBX.

The “nonce” value is also supposed to be returned by the media engine when it retries the SIP request – and its not there.

We are looking at this right now. We will post again to this forum thread when we locate the issue.

Support

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 07 2007 at 7:39pm | IP Logged Quote support
Hi Jalal,

Ok, here is what we have found.

The nonce double quoted string values are the strangest nonce values we have ever seen from a SIP 2.x compliant device. The problem is associated with how the media engine parses the nonce value strings from the “WWW-Authenticate:” header.

The same parsing problem will be experienced if the Mitel IP PBX also uses a similar kind of nonce value for “Proxy-Authenticate:” headers when calls are initiated or terminated.

We updated the authentication header parsing code and ran tests. The data used to compute the challenge responses is now being parsed properly from received “WWW-Authenticate:” and “Proxy-Authenticate:” headers – using the Mitel nonce formats.

What we have to do now is actually have you test the code changes against the Mitel 3300 IP PBX.

There could still be another issue but we need to at least see where we are at with this latest build.

We have updated your support FTP account with the media engine that has the new changes. You should be able to simply overwrite your current v5.12.3.27 image with the new v5.12.3.28 image (Make a copy of your existing v5.12.3.27 image before you overwrite it). This new DLL image should only be used for short term testing. We will re-issue a product image if all is well with the current changes.

Seeing we had to make available to you a new revision, we also made the appropriate changes to resolve the issues you reported for the following posts:

StartPhoneLineRecording RecordDirectory parameter:
http://www.lanscapecorp.com/forum/forum_posts.asp?TID=269&PN =1

…and we also added the “wild card” realm support as described at the end of this post:
http://www.lanscapecorp.com/forum/forum_posts.asp?TID=316&TP N=1


Please download and test this latest build and repost back to this thread. We need to know if the authentication parser changes are working for the Mitel IP PBX.

Thanks,

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 07 2007 at 7:40pm | IP Logged Quote support
By the way, great work in posting your initial information. Accuracy in the problem description really helps.

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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 08 2007 at 5:40am | IP Logged Quote Jalal
Hi,

We have checked your new version but again we receive SIP 403 Forbidden message.

This is the log of new test.
Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, 0 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fb1b0f
From: <sip:9090@192.168.0.241>;tag=8fabaae
To: <sip:9090@192.168.0.241>
Call-Id: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436774 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.91:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.28 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fb1b0f
From: <sip:9090@192.168.0.241>;tag=8fabaae
To: <sip:9090@192.168.0.241>;tag=MitelICP_2660976272-56863 441
Call-ID: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436774 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fb1b0f
WWW-Authenticate: Digest realm="XIRA CORP",nonce="#MA[efh}fU%[r7D>!xs-sN)LZ<Eq^xD`R!&'eet[hHR4Hk(S|*c%`tKXN-h|d",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=8fabaae
To: <sip:9090@192.168.0.241>;tag=MitelICP_2660976272-56863 441
Call-ID: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436774 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, 46 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fab654
From: <sip:9090@192.168.0.241>;tag=8fb2a93
To: <sip:9090@192.168.0.241>
Call-Id: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436775 REGISTER
Authorization: Digest algorithm=md5, cnonce="00fac4b3", nc="00000001", nonce="#MA[efh}fU%[r7D>!xs-sN)LZ<Eq^xD`R!&'eet[hHR4Hk(S|*c%`tKXN-h|d", qop="auth", realm="XIRA CORP", response="a8b37a97bef978593130a962aa810065", uri="sip:192.168.0.241", username="9090"
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.91:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.28 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, 32 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fab654
From: <sip:9090@192.168.0.241>;tag=8fb2a93
To: <sip:9090@192.168.0.241>;tag=MitelICP_2661006272-56863 442
Call-ID: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436775 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.0.91:5061;rport;branch=z9hG4bK08fab654
From: <sip:9090@192.168.0.241>;tag=8fb2a93
To: <sip:9090@192.168.0.241>;tag=MitelICP_2661006272-56863 442
Call-ID: aa772676-9ac2-4294-b81f-63366d7fef97-000014b8@192.168.0.91
CSeq: 16436775 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0



I think it's better to compare this new log with previous log of Phone free (See first post of this thread). Maybe again double quates is the problem because for example Phoner Free sends nc=00000001 and you send nc="00000001". Also the order of "Authorization:" section parameters maybe another problem.

Regards,
Jalal

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 6:08am | IP Logged Quote support
Hi Jalal,

We will start working on this immediately this morning. We will no doubt locate the issue with further investigation. The sooner we get authentication and basic call inter-op working, the better.

SIP inter-op sometimes is always a bit "touch and go" when first communicating with a new SIP device.

Is there any chance that we may access the Mitel IP PBX from the LanScape testing lab? That way we can perform tests immediately. If the PBX is behind your firewall, we can give you our WAN IP address so that you can momentarily let us past your firewall at your end.


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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 08 2007 at 6:17am | IP Logged Quote Jalal
Hi,

Unfortunately accessing the Mitel PBX directly is impossible now because of our customer restrictions. But one of our developers is currently on the site. He is trying to change your sending SIP Register packet for different states. If you have any suggestion he can test now.

You may also provide us any new LMEVoip.DLL to test if you think it helps. He will be on the site up to next 3 hours.

Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 6:26am | IP Logged Quote support
Jalal,

Well then ask the customer to temporarily lift the access restrictions. We are trustworthy.

We will try to identify possible causes and get you updated media engine DLL as soon as we can. Not being able to access the equipment directly will slow down the entire testing process.

If your “on site” person thinks he has located the problem, let us know as soon as possible.

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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 08 2007 at 8:17am | IP Logged Quote Jalal
Hi,

Forget about connecting directly to Mitel because it is not possible.

Unfortunately we can not change Authorization part of SIP Register. When we change this part it seems Media Engine ignores our changes. We checked both Media Engine's logs and Ethereal logs. What's the matter with this?

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 8:23am | IP Logged Quote support
Jalal,

Not sure what you mean when you say "we can not change Authorization part of SIP Register".

Can you elaborate?

Also, we are testing our changes for you right now...


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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 08 2007 at 8:43am | IP Logged Quote Jalal
We are changing Authorization parameters in REGISTER sip message with your ModifySipMessage function when SipModifySipMessage event is received. For example we replace nc="00000001" with nc=00000001 but it seems Media Engine ignores our changes or rechanges our modified message.

I hope I could explain better.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 8:51am | IP Logged Quote support
That makes good sense.

Hmmm....
For a SIP message that is ready to be transmitted (regardless if it has computed authentication info), you should be able to change the entire contents of the SIP message.
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 9:23am | IP Logged Quote support
Jalal,

We just thought of something that may help us:

If the media engine is taking your outgoing modified SIP message and forcing a particular format for some parameters, you can achieve your test results if you tell the media engine to ignore the ready to be transmitted SIP message by setting the IgnoreSipMessage member in the SIP_MESSAGE_IMMEDIATE_DATA structure that gets passed to your app.

Now what you want to do is send the modified Sip message yourself uing the new API procedure SendUdpDatagramUsingSipPort(). This new procedure will send your SIP message using the SIP port of the media engine without any changes.


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 08 2007 at 6:52pm | IP Logged Quote support
Jalal,

The problem with the inter-op authentication with the Mitel 3300 IP PBX was a combination of things.

For starters, the nonce value the Mitel guys generate in their authentication challenges uncovered a parsing issue in the media engine. Embedding ‘=’ and ‘,’ characters in a double quoted string was the problem. We have never seen a nonce value like the one they generate. However it looks valid as far as the RFC goes.

Since we were looking at and reviewing the way we handle all the authentication parameters, we also saw that when the media engine is qop challenged, the nonce count and the qop type we returned were being double quoted. Normally this has been ok. Mitel doesn’t appear to like this. There is a bit of confusion between SIP implementations regarding this and what is stated in RFC 2617. We have removed the double quotes around the appropriate parameters as per the RFC. We still need to back track and now inter-op test so we don’t break any other inter-op.

We will make available an updated DLL image for your testing. Download it when you can.

The VPN connection from our lab to the customer worked great and allowed us to perform all needed tests.

We may want to access this IP PBX a bit later to verify final inter-op so we will coordinate this with you. We may want to perform additional testing with call hold and un-hold operations. If you have any documentation on what SIP message flows the PBX generates when a UA puts a call on hold, that would be good. It seems that the PBX generates a number of consecutive INVITE requests that are a bit confusing to us. We are not sure what they are all for.

Here is a SIP log between extension 9090 and 9091 with authentication enabled using uLaw:

Code:

************* Log Opened (May 08 18:25:21) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#18, 9046 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbe26
From: <sip:9090@192.168.0.241>;tag=2dd667e
To: <sip:9090@192.168.0.241>
Call-Id: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479691 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#27, 9343 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbe26
From: <sip:9090@192.168.0.241>;tag=2dd667e
To: <sip:9090@192.168.0.241>;tag=MitelICP_2659444128-56863 042
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479691 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#28, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbe26
WWW-Authenticate: Digest realm="XIRA CORP",nonce="D9y8+=)p1~`0R)1%;R(-SeB_TTt9vDoMUZ}{b?}A]Ld4tB. ?AJMIUaJ=0m_zIdy[",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=2dd667e
To: <sip:9090@192.168.0.241>;tag=MitelICP_2659444128-56863 042
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479691 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#19, 297 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd9319
From: <sip:9090@192.168.0.241>;tag=2ddac4f
To: <sip:9090@192.168.0.241>
Call-Id: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479692 REGISTER
Authorization: Digest algorithm=md5,cnonce="00dd7868",nc=00000001,nonce="D9y8+=)p1 ~`0R)1%;R(-SeB_TTt9vDoMUZ}{b?}A]Ld4tB.?AJMIUaJ=0m_zIdy[",qop =auth,realm="XIRA CORP",response="dde0cb93e64993e3af83a11e4fab8b4e",uri="sip:1 92.168.0.241",username="9090"
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#29, 313 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd9319
From: <sip:9090@192.168.0.241>;tag=2ddac4f
To: <sip:9090@192.168.0.241>;tag=MitelICP_2659754128-56863 043
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479692 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#30, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd9319
From: <sip:9090@192.168.0.241>;tag=2ddac4f
To: <sip:9090@192.168.0.241>;tag=MitelICP_2659754128-56863 043
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479692 REGISTER
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Contact: <sip:9090@192.168.0.9:5062>;expires=3600
Expires: 0
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#20, 1375 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd89ee
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddce66;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>
Contact: <sip:9090@192.168.0.9:5062>;x-inst="VGVzdCBDYWxsIERhdG EgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515256 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 48060093 48060093 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 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 (#31, 1359 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd89ee
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddce66;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661124128-56863 044
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515256 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#32, 16 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd89ee
WWW-Authenticate: Digest realm="XIRA CORP",nonce="qkd6)7P:}yS[}eluHfmR)G-yJF5L*E{SG2EBK6`u-9a42gP*M,&]y0Q.)^&!l^;J",algorithm=MD5,qop="auth"
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddce66;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661124128-56863 044
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515256 INVITE
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#21, 313 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd89ee
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddce66;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661124128-56863 044
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515256 ACK
Max-Forwards: 70
Route: <sip:192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#22, 0 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd8b27
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>
Contact: <sip:9090@192.168.0.9:5062>;x-inst="VGVzdCBDYWxsIERhdG EgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515569 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Authorization: Digest algorithm=md5,cnonce="00dda923",nc=00000001,nonce="qkd6)7P:} yS[}eluHfmR)G-yJF5L*E{SG2EBK6`u-9a42gP*M,&]y0Q.)^&!l^;J",qop=auth,realm="XIRA CORP",response="d1bf71d875529ff4f47fe5a34f1c7535",uri="sip:9 091@192.168.0.241",username="9090"
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 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 (#33, 328 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd8b27
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515569 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#34, 62 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd8b27
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515569 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#35, 1844 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd8b27
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515569 INVITE
Supported: timer
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 129

v=0
o=- 14549922960798082688 14549922960798082688 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8614 RTP/AVP 0


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#23, 2234 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02dd8b27
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515569 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#24, 1610 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddd0b1
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Contact: <sip:9090@192.168.0.9:5062>
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515570 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 217
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 48064250 48064250 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8908 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 (#36, 1922 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddd0b1
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515570 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#37, 328 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddd0b1
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515570 INVITE
Supported: timer
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Content-Length: 194

v=0
o=- 14549922960798082688 14549922960798082689 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 0 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=inactive


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#25, 640 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddd0b1
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515570 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#26, 1297 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddebb7
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Contact: <sip:9090@192.168.0.9:5062>
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515571 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 48066187 48066187 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 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 (#38, 1594 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddebb7
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515571 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#39, 500 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddebb7
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515571 INVITE
Supported: timer
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Content-Length: 207

v=0
o=- 14549922960798082688 14549922960798082690 IN IP4 0.0.0.0
s=-
c=IN IP4 0.0.0.0
t=0 0
m=audio 9000 RTP/AVP 0 101
c=IN IP4 0.0.0.0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#27, 797 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddebb7
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 14515571 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#40, 312 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2668014128-56863064
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 2 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 129

v=0
o=- 14549922960798082688 14549922960798082691 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8614 RTP/AVP 0


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#28, 312 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2668 014128-56863064
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 2 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 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 (#41, 297 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2668324128-56863065
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 2 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#42, 2750 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2671064128-56863070
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 3 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 141

v=0
o=- 14549922960798082688 14549922960798082692 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8614 RTP/AVP 0
a=sendonly


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#29, 3047 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2671 064128-56863070
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 3 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#43, 313 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2671374128-56863071
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 3 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#44, 0 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2671374128-56863072
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 4 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 138

v=0
o=- 14549922960798082688 14549922960798082693 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 0 RTP/AVP 0
a=inactive


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#30, 313 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2671 374128-56863072
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 4 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#45, 312 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2671694128-56863073
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 4 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#46, 0 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2671694128-56863074
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 5 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#31, 328 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2671 694128-56863074
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 5 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#47, 360 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2672044128-56863075
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 5 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 202

v=0
o=- 14549922960798082688 14549922960798082694 IN IP4 192.168.0.240
s=-
c=IN IP4 192.168.0.240
t=0 0
m=audio 50036 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#48, 1515 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2673574128-56863076
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 6 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 198

v=0
o=- 14549922960798082688 14549922960798082695 IN IP4 192.168.0.240
s=-
c=IN IP4 192.168.0.240
t=0 0
m=audio 0 RTP/AVP 0 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=inactive


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#32, 1859 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2673 574128-56863076
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 6 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#49, 313 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2673884128-56863077
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 6 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#50, 15 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2673884128-56863078
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 7 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 129

v=0
o=- 14549922960798082688 14549922960798082696 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8614 RTP/AVP 0


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#33, 328 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2673 884128-56863078
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 7 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 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 (#51, 313 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2674204128-56863079
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 7 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#52, 6125 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2680334128-56863082
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 8 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 141

v=0
o=- 14549922960798082688 14549922960798082697 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8614 RTP/AVP 0
a=sendonly


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#34, 6438 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2680 334128-56863082
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 8 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 221
Content-Type: application/sdp

v=0
o=9090 48060406 48060406 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8908 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#53, 297 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2680634128-56863083
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 8 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#54, 15 Ms, From: 192.168.0.241:5060) <<<<
BYE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK2680634128-56863084
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 9 BYE
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#35, 312 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK2680 634128-56863084
From: <sip:9091@192.168.0.241>;tag=MitelICP_2661454128-56863 045;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2ddcf9f;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: bde3605a-991f-4a00-a2ce-84faba60e745-00004900@192.168.0.9
CSeq: 9 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#36, 1219 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddb4a7
From: <sip:9090@192.168.0.241>;tag=2ddaadf
To: <sip:9090@192.168.0.241>
Call-Id: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479693 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#55, 1516 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddb4a7
From: <sip:9090@192.168.0.241>;tag=2ddaadf
To: <sip:9090@192.168.0.241>;tag=MitelICP_2682164128-56863 085
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479693 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#56, 16 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddb4a7
WWW-Authenticate: Digest realm="XIRA CORP",nonce="vjIX;hWED}Ry]=PRU![/8/Sv~2;p;b(owm0_ROXhWIme=X3 <=hpOl-B3_Pv[H5Ia",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=2ddaadf
To: <sip:9090@192.168.0.241>;tag=MitelICP_2682164128-56863 085
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479693 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#37, 313 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbd08
From: <sip:9090@192.168.0.241>;tag=2ddd8d3
To: <sip:9090@192.168.0.241>
Call-Id: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479694 REGISTER
Authorization: Digest algorithm=md5,cnonce="00ddbf8a",nc=00000001,nonce="vjIX;hWED }Ry]=PRU![/8/Sv~2;p;b(owm0_ROXhWIme=X3<=hpOl-B3_Pv[H5Ia", qop=auth,realm="XIRA CORP",response="a47db7166c4cae9fd986efeabd10a82c",uri="sip:1 92.168.0.241",username="9090"
Expires: 0
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#57, 297 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbd08
From: <sip:9090@192.168.0.241>;tag=2ddd8d3
To: <sip:9090@192.168.0.241>;tag=MitelICP_2682474128-56863 086
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479694 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#58, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02ddbd08
From: <sip:9090@192.168.0.241>;tag=2ddd8d3
To: <sip:9090@192.168.0.241>;tag=MitelICP_2682474128-56863 086
Call-ID: 77471f87-02b7-459f-a0e9-b9360ee05d85-00004900@192.168.0.9
CSeq: 14479694 REGISTER
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Expires: 0
Content-Length: 0


************* Log Closed (May 08 18:25:49) *************




Here is a SIP log between extension 9090 and 9091 with authentication enabled using G729:

Code:

************* Log Opened (May 08 18:49:25) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#76, 5578 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c2de
From: <sip:9090@192.168.0.241>;tag=2f36b27
To: <sip:9090@192.168.0.241>
Call-Id: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616863 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#104, 5562 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c2de
From: <sip:9090@192.168.0.241>;tag=2f36b27
To: <sip:9090@192.168.0.241>;tag=MitelICP_4102364128-56863 269
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616863 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#105, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c2de
WWW-Authenticate: Digest realm="XIRA CORP",nonce="wbiGl4BJg`x}kNtbIdckRzdMMZLE0'<(|ST(2V$>F NoVi,m^);.eb&&*S{#PJ.-e",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=2f36b27
To: <sip:9090@192.168.0.241>;tag=MitelICP_4102364128-56863 269
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616863 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#77, 297 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f397d1
From: <sip:9090@192.168.0.241>;tag=2f3b107
To: <sip:9090@192.168.0.241>
Call-Id: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616864 REGISTER
Authorization: Digest algorithm=md5,cnonce="00f37d20",nc=00000001,nonce="wbiGl4BJg `x}kNtbIdckRzdMMZLE0'<(|ST(2V$>FNoVi,m^);.eb&&*S{#PJ.- e",qop=auth,realm="XIRA CORP",response="07056f97a325602a86788b3488009358",uri="sip:1 92.168.0.241",username="9090"
Expires: 3600
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#106, 313 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f397d1
From: <sip:9090@192.168.0.241>;tag=2f3b107
To: <sip:9090@192.168.0.241>;tag=MitelICP_4102674128-56863 270
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616864 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#107, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f397d1
From: <sip:9090@192.168.0.241>;tag=2f3b107
To: <sip:9090@192.168.0.241>;tag=MitelICP_4102674128-56863 270
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616864 REGISTER
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Contact: <sip:9090@192.168.0.9:5062>;expires=3600
Expires: 0
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#78, 3000 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f377df
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d72f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>
Contact: <sip:9090@192.168.0.9:5062>;x-inst="VGVzdCBDYWxsIERhdG EgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964522 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 223
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 49504718 49504718 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8342 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#108, 2984 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f377df
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d72f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105664128-56863 271
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964522 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#109, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f377df
WWW-Authenticate: Digest realm="XIRA CORP",nonce="<GVwdS}BC!.B7Uae}sn]pa$[2HBYdER|8h'1pJ~_2Hk! .i;8Gf{86_3|R$6YbUNS",algorithm=MD5,qop="auth"
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d72f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105664128-56863 271
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964522 INVITE
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#79, 313 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f377df
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d72f;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105664128-56863 271
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964522 ACK
Max-Forwards: 70
Route: <sip:192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#80, 0 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f37918
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>
Contact: <sip:9090@192.168.0.9:5062>;x-inst="VGVzdCBDYWxsIERhdG EgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964835 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Authorization: Digest algorithm=md5,cnonce="00f3a124",nc=00000001,nonce="<GVwdS }BC!.B7Uae}sn]pa$[2HBYdER|8h'1pJ~_2Hk!.i;8Gf{86_3|R$6YbUNS", qop=auth,realm="XIRA CORP",response="2896e3cc3db74aac2d98e70436668c6d",uri="sip:9 091@192.168.0.241",username="9090"
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 223
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 49505031 49505031 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8342 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#110, 328 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f37918
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964835 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#111, 63 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f37918
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964835 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#112, 1375 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f37918
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964835 INVITE
Supported: timer
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 174

v=0
o=- 14549929162790858112 14549929162790858112 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8144 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#81, 1750 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f37918
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964835 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#82, 8734 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3ebe0
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Contact: <sip:9090@192.168.0.9:5062>
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964836 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 219
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 49515515 49515515 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8342 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#113, 9031 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3ebe0
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964836 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#114, 328 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3ebe0
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964836 INVITE
Supported: timer
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Content-Length: 239

v=0
o=- 14549929162790858112 14549929162790858113 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 0 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=inactive


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#83, 625 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3ebe0
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964836 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#84, 1797 Ms, To: 192.168.0.241:5060) >>>>
INVITE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3d4ec
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Contact: <sip:9090@192.168.0.9:5062>
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964837 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 223
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9090 49517937 49517937 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8342 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#115, 2110 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3d4ec
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964837 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#116, 500 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3d4ec
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964837 INVITE
Supported: timer
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Type: application/sdp
Content-Length: 252

v=0
o=- 14549929162790858112 14549929162790858114 IN IP4 0.0.0.0
s=-
c=IN IP4 0.0.0.0
t=0 0
m=audio 9000 RTP/AVP 18 101
c=IN IP4 0.0.0.0
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#85, 813 Ms, To: 192.168.0.241:5060) >>>>
ACK sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3d4ec
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964837 ACK
Max-Forwards: 70
Route: <sip:9091@192.168.0.241>
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#117, 296 Ms, From: 192.168.0.241:5060) <<<<
INVITE sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK4119694128-56863287
Max-Forwards: 70
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Supported: timer,replaces
From: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 2 INVITE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 174

v=0
o=- 14549929162790858112 14549929162790858115 IN IP4 192.168.0.9
s=-
c=IN IP4 192.168.0.9
t=0 0
m=audio 8144 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#86, 296 Ms, To: 192.168.0.241:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.241:5060;received=192.168.0.241;branch=z9hG4bK4119 694128-56863287
From: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 2 INVITE
Contact: <sip:9090@192.168.0.9:5062>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
Content-Length: 223
Content-Type: application/sdp

v=0
o=9090 49505031 49505031 IN IP4 192.168.0.9
s=LanScape
c=IN IP4 192.168.0.9
t=0 0
m=audio 8342 RTP/AVP 18 101
a=rtpmap:18 G729/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#118, 313 Ms, From: 192.168.0.241:5060) <<<<
ACK sip:9090@192.168.0.9:5062 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.241:5060;branch=z9hG4bK4120004128-56863288
Max-Forwards: 70
From: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272;x-UaId=xxxxx-yyyy-zzzzzz
To: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 2 ACK
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#87, 5922 Ms, To: 192.168.0.241:5060) >>>>
BYE sip:9091@192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f41382
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272
Call-Id: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964838 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#119, 5922 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f41382
From: "Extension 9090" <sip:9090@192.168.0.241>;tag=2f3d868;x-UaId=xxxxx-yyyy -zzzzzz
To: <sip:9091@192.168.0.241>;tag=MitelICP_4105994128-56863 272;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 2dc4a79a-67ce-4158-919b-c09bc4c03f82-000069b8@192.168.0.9
CSeq: 15964838 BYE
Contact: <sip:9091@192.168.0.241:5060;transport=udp>
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#88, 1125 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c100
From: <sip:9090@192.168.0.241>;tag=2f3b738
To: <sip:9090@192.168.0.241>
Call-Id: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616865 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#120, 1109 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c100
From: <sip:9090@192.168.0.241>;tag=2f3b738
To: <sip:9090@192.168.0.241>;tag=MitelICP_4127034128-56863 296
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616865 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#121, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c100
WWW-Authenticate: Digest realm="XIRA CORP",nonce="|hs4]K-kgllb);!t0}k=XbuPhv2<SU;N_.YnaxnU2}A. ]_~d-=r+0'xr.x#_gYwJ",algorithm=MD5,qop="auth"
From: <sip:9090@192.168.0.241>;tag=2f3b738
To: <sip:9090@192.168.0.241>;tag=MitelICP_4127034128-56863 296
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616865 REGISTER
Contact: <sip:192.168.0.241>
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#89, 297 Ms, To: 192.168.0.241:5060) >>>>
REGISTER sip:192.168.0.241 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c951
From: <sip:9090@192.168.0.241>;tag=2f3e51c
To: <sip:9090@192.168.0.241>
Call-Id: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616866 REGISTER
Authorization: Digest algorithm=md5,cnonce="00f3cbd3",nc=00000001,nonce="|hs4]K-kg llb);!t0}k=XbuPhv2<SU;N_.YnaxnU2}A.]_~d-=r+0'xr.x#_gYwJ", qop=auth,realm="XIRA CORP",response="0699a3d2a4e5260afb2da19e9401a967",uri="sip:1 92.168.0.241",username="9090"
Expires: 0
Max-Forwards: 70
Contact: <sip:9090@192.168.0.9:5062>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.29 (www.LanScapeCorp.com)
x-CustomHeader-Extension-9090: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#122, 313 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c951
From: <sip:9090@192.168.0.241>;tag=2f3e51c
To: <sip:9090@192.168.0.241>;tag=MitelICP_4127344128-56863 297
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616866 REGISTER
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#123, 0 Ms, From: 192.168.0.241:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.9:5062;rport;branch=z9hG4bK02f3c951
From: <sip:9090@192.168.0.241>;tag=2f3e51c
To: <sip:9090@192.168.0.241>;tag=MitelICP_4127344128-56863 297
Call-ID: 5fef9c02-28ea-486d-961a-1e93af41f742-000069b8@192.168.0.9
CSeq: 15616866 REGISTER
Allow: INVITE,BYE,CANCEL,ACK,INFO,PRACK,COMET,OPTIONS,SUBSCRIBE,NOT IFY,MESSAGE,REFER,REGISTER,UPDATE
Expires: 0
Content-Length: 0


************* Log Closed (May 08 18:49:54) *************


That’s all for now,

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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 09 2007 at 2:58am | IP Logged Quote Jalal
Hi,

Thanks for your new version. The Authentication problem is solved now. But unfortunately as you mentioned we have some problem regarding Hold/Unhold.

We have requested our customer to leave the VPN connection open for another day and he has accepted. So you may continue inter-op test today.

Thanks again.
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal's Homepage
 
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 09 2007 at 12:23pm | IP Logged Quote Jalal
Hi

Please inform me of the status of your tests on Mitel.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 09 2007 at 1:34pm | IP Logged Quote support
Hi Jalal,

We are done with testing using the Mitel. You can terminate the VPN access. We wanted to do a bit of comparison inter-op testing with other VOIP software and user agents we have. We wanted to make sure the SIP message flows are similar between different SIP implementations.

The SIP message flows for basic call operations including hold and un-hold are the same for other SIP devices registered with the Mitel as they are for the VOIP Media Engine.

The last media engine image you grabbed via FTP must be replaced – its time bombed. We will get you a new product image ready for download. We will send you an email when it is ready.

Be sure to thank the people at XIRA for allowing us to access the Mitel.


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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 09 2007 at 11:48pm | IP Logged Quote Jalal
Hi,

Really thanks for your coperation. I will ask XIRA guys to ask about HOLD/UNHOLD problem from
Mitel. They are Mitel partner in Iran. I will report you later about this in current thread.

Please put the latest image in our FTP on Friday because we are not at office till saturday.

Please also put the latest image for .Net edition in our FTP server if it is possible.

Best Regards,
Jalal
Back to Top View Jalal's Profile Search for other posts by Jalal Visit Jalal'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