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: Phone Call itself problem Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
mfitzgerald
Vetran
Vetran


Joined: June 14 2006
Location: United States
Posts: 142
Posted: January 22 2007 at 6:17pm | IP Logged Quote mfitzgerald
I’ve come across a possible issue with Lanscape (LS). I’m not certain how to interoperate the results. I’ll have to perform more tests on this attempt tomorrow.

We are using the Multi-line phone app with two phone lines enabled. We have the need to develop a soft-phone application that calls itself.

I’ve included the ini file as it exists with all settings.

As specified in the LanScape documentation, to get multiple extensions for each phone line, you use a comma delimited string as the second argument in EnableSipRegisterServer() function as follows. (This has been hard coded for now)

Code:

CString PhoneNames = "269999,269998";
                                 if(PhoneBaseSettings.UseRegistrationServer && PhoneBaseSettings.UseDomainName)
           {
           // register with the registrar. we assume here that the SIP proxy
           // supports registrar functiuons.
                status = EnableSipRegisterServer(
                      pCPhoneBase->hSipEngine,
                      CSPTR(PhoneNames),
                      FALSE,
                      FALSE,
                CSPTR(PhoneBaseSettings.Regist rationServerAddress),
                PhoneBaseSettings.Registration ServerPort,
                PhoneBaseSettings.Registration IntervalSeconds,
                PhoneBaseSettings.Registration IntervalSeconds,
                PhoneBaseSettings.Registration TimeoutMs,
                      FALSE
                );


Ini file settings:
Code:

[Settings]
PhoneName=269999
PhoneDisplayName=LanScape Phone
LocalSipPort=5060
CurrentIpAddress=172.26.253.176
SipDomainEnabled=1
SipDomainName=10.2.2.75
UseRegistrationServer=1
RegistrationServerAddress=10.2.2.75
RegistrationServerPort=5060
RegistrationIntervalSeconds=3600
RegistrationTimeoutMs=4000
UseSipProxy=1
SipProxyAddress=10.2.2.75
SipProxyPort=5060
SipKeekAliveEnabled=1
WanIpAddressEnabled=0
WanIpAddress=
RtpPortMin=8000
RtpPortMax=8998
PlaybackBufferingDefault=2
PlaybackBufferingDuringSounds=4
PhoneLineTransmitBuffering=2
AuthEnabled=0
AuthRealm=MyDomain.com
AuthUsername=username
AuthPassword=password
MicrocodeFilePath=C:\home\projects\VolleyBall\Microcode\LanS capeVME.C
SipLogServer=localhost:1002
AppWindowLeft=610
AppWindowRight=599
AppWindowTop=1239
AppWindowBottom=999
PhoneLineRecordEnabled=0
PhoneLineRecordDirectory=


As you’ll see in the included SIP Log, the two phone extensions register correctly. Then an attempted call is made from 269999 to 269998. The INVITE goes out as expected, ringing and trying. The respective INVITE comes back from the PBX.

However there is no indication of an incoming call with the Multi-Line Phone App. (I’ll have to put some break points for an incoming invite in the TelephonyEngineCallback() just to be certain LS recognized the INVITE request – testing tomorrow).

No further indication of anything occurs for another 45 seconds, until apparently the PBX times out and sends a 480.


This test had previously been performed with LS registered as 269999 and a 3rd party soft-phone registered as 269998 with the same settings as indicated and registered with the PBX accordingly. The test in this case was for phone 269998 to call 269999. The test proved successful.

At first glance, it would appear as the LS Media Engine was confused and didn’t know how to act on the incoming INVITE from itself. I don’t know for certain.

Thanks


SIP Log
Code:


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c3eaeb
From: <sip:269999@10.2.2.75>;tag=15c3ce6d
To: <sip:269999@10.2.2.75>
Call-Id: 6b80424c-e990-4670-b2b4-df98a948134e-00000a40@172.26.253.176
CSeq: 12837883 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:269999@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c3eaeb
To: <sip:269999@10.2.2.75>;tag=t1169506025-co517
From: <sip:269999@10.2.2.75>;tag=15c3ce6d
Call-ID: 6b80424c-e990-4670-b2b4-df98a948134e-00000a40@172.26.253.176
CSeq: 12837883 REGISTER
Expires: 3600
Contact: <sip:269999@172.26.253.176:5060>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP1989-CO517-CPO00000
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (31 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c40b5d
From: <sip:269998@10.2.2.75>;tag=15c43320
To: <sip:269998@10.2.2.75>
Call-Id: 6b80424c-e990-4670-b2b4-df98a948134e-00000a40@172.26.253.176
CSeq: 12837884 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:269998@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (32 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c40b5d
To: <sip:269998@10.2.2.75>;tag=t1169506025-co520
From: <sip:269998@10.2.2.75>;tag=15c43320
Call-ID: 6b80424c-e990-4670-b2b4-df98a948134e-00000a40@172.26.253.176
CSeq: 12837884 REGISTER
Expires: 3600
Contact: <sip:269998@172.26.253.176:5060>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2035-CO520-CPO00000
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (9969 Ms, To: 10.2.2.75:5060) >>>>
INVITE sip:269998@l10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c43f74
From: "LanScape Phone" <sip:269999@10.2.2.75>;tag=15c4083f
To: <sip:269998@l10.2.2.75>
Contact: <sip:269999@172.26.253.176:5060>
Call-Id: 093bcf04-8632-4dd6-9583-77baf63dde7b-00000a40@172.26.253.176
CSeq: 12856040 INVITE
Max-Forwards: 70
Organization: C7287C3C-834E-410A-90FF-497C30F94945
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 233
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=269999 365163250 365163250 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 172.26.253.176
t=0 0
m=audio 8180 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



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (9953 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c43f74
To: <sip:269998@l10.2.2.75>
From: "LanScape Phone" <sip:269999@10.2.2.75>;tag=15c4083f
Call-ID: 093bcf04-8632-4dd6-9583-77baf63dde7b-00000a40@172.26.253.176
CSeq: 12856040 INVITE
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP1989-CO611-CPO00000
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (15 Ms, From: 10.2.2.75:5060) <<<<
INVITE sip:269998@172.26.253.176:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b53ef3-265-1
To: <sip:269998@172.26.253.176:5060>
From: "LanScape Phone" <sip:269999@10.2.2.75:5060>;tag=t1169506035-co613
Date: Mon, 22 Jan 2007 22:47:15 GMT
Call-ID: 093bcf04-8632-4dd6-9583-77baf63dde7b-00000a40@172.26.253.176
CSeq: 24390 INVITE
Max-Forwards: 70
X-XLData: pc=843303;dnis=269998
Contact: <sip:269999@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2035-CO613-CPO01278
Content-Type: application/sdp
Content-Length: 224

v=0
o=- 2131481438 1879823198 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8180 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv


<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (45829 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c43f74
To: <sip:269998@l10.2.2.75>;tag=t1169506035-co611
From: "LanScape Phone" <sip:269999@10.2.2.75>;tag=15c4083f
Call-ID: 093bcf04-8632-4dd6-9583-77baf63dde7b-00000a40@172.26.253.176
CSeq: 12856040 INVITE
Reason: Q.850 ;cause=31 ;text="Unknown"
Contact: <sip:269998@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP1989-CO611-CPO01277
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (45938 Ms, To: 10.2.2.75:5060) >>>>
ACK sip:269998@l10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK15c43f74
From: "LanScape Phone" <sip:269999@10.2.2.75>;tag=15c4083f
To: <sip:269998@l10.2.2.75>;tag=t1169506035-co611
Call-Id: 093bcf04-8632-4dd6-9583-77baf63dde7b-00000a40@172.26.253.176
CSeq: 12856040 ACK
Max-Forwards: 70
Route: <sip:269998@10.2.2.75>
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: January 23 2007 at 7:33am | IP Logged Quote support
Hi Fitz,

We will look into it. Good problem description. Post other test info as you gather it.

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


Joined: June 14 2006
Location: United States
Posts: 142
Posted: January 23 2007 at 11:48am | IP Logged Quote mfitzgerald
Further tests:
Test 1:

With the test in the previous post (LS calling itself) - (same SIP Message results). This time values were logged at specific points in the PyhoneBase.cpp

TelephonyEngineCallback()
At the beginning of this function to display exactly the TelephonyEvent value
And where NotificationType == IMMEDIATE_NOTIFICATION and the TelephonyEvent was SipModifySipMessage and pSipMessageImmediateData->Received and the SIP Message was an INVITE.

and

EventThreadCallback()
Additional points of interest were placed in the where NotificationType == GLOBAL_NOTIFICATION and “Phone line specific state changes” These points would display the SipStatus value.

The incoming INVITE as mentioned in the previous post was received by the TelephonyEngineCallback() as expected.
In EventThreadCallback only the Global Notifications were hit (Send Invite and Wait for Invite OK) respectively.

No Event Callback indicating the incoming Invite message was indicated.

Test 2:
3rd party phone calling (on it’s line 0) one phone line/extension of LS, while that call is active, start another call on LS’s line 1.

(3rd prty) 269997 (line 0) - -> invites - -> (LS line 0) 269999
(3rd prty) 269997 (line 1) - -> invites - -> (LS line 1) 269998

This proved successful. The incoming Invite events were received this time; LS automatically put line 0 on hold when line 1 was answered.

This does appear to be a LS issue.

Thanks as always for your prompt attention and responses.



3rd party phone SIP Messages
Code:

============================================================ =========
Time:         & nbsp;10:42:03.43
Type:         & nbsp;SIPOutgoing
Description:     REGISTER
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK9EC49C9C3FFD4EB48F31800E37 EFEDBA
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
To: "269997" <sip:269997@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4507 REGISTER
Expires: 1800
Allow: INVITE,ACK,CANCEL,REFER,BYE,NOTIFY,OPTIONS,INFO
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:03.44
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK9EC49C9C3FFD4EB48F31800E37 EFEDBA
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570523-co1360
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4507 REGISTER
Expires: 1800
Contact: <sip:269997@172.26.253.176:5061>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO1360-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:12.04
Type:         & nbsp;SIPOutgoing
Description:     INVITE
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

INVITE sip:269999@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC4DBD56BE5CD4CC193AD94635E 33A021
From: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
To: <sip:269999@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 9525 INVITE
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 347
Content-Type: application/sdp

v=0
o=269997 633051457320270632 633051457320270650 IN IP4 172.26.253.176
s=WOSI SIP 0.5
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 0 8 3 98 7 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:7 LPC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



============================================================ =========
Time:         & nbsp;10:42:12.05
Type:         & nbsp;SIPIncoming
Description:     100 Trying
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC4DBD56BE5CD4CC193AD94635E 33A021
To: <sip:269999@10.2.2.75>
From: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 9525 INVITE
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO1428-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:12.10
Type:         & nbsp;SIPIncoming
Description:     180 Ringing
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC4DBD56BE5CD4CC193AD94635E 33A021
To: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
From: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 9525 INVITE
Contact: <sip:269999@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:14.68
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC4DBD56BE5CD4CC193AD94635E 33A021
To: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
From: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 9525 INVITE
Contact: <sip:269999@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Type: application/sdp
Content-Length: 156

v=0
o=- 2134569223 1429926151 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000
a=sendrecv


============================================================ =========
Time:         & nbsp;10:42:14.74
Type:         & nbsp;SIPOutgoing
Description:     ACK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

ACK sip:269999@10.2.2.75:5060 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK8654FC6C246643AD82617FE29F D1A83A
From: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
To: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 9525 ACK
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:29.65
Type:         & nbsp;SIPOutgoing
Description:     INVITE
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

INVITE sip:269998@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC628120381484FED9FBC7FE7D1 F341E8
From: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
To: <sip:269998@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 3179 INVITE
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 347
Content-Type: application/sdp

v=0
o=269997 633051457496522888 633051457496522906 IN IP4 172.26.253.176
s=WOSI SIP 0.5
c=IN IP4 172.26.253.176
t=0 0
m=audio 8000 RTP/AVP 18 0 8 3 98 7 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:7 LPC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



============================================================ =========
Time:         & nbsp;10:42:29.66
Type:         & nbsp;SIPIncoming
Description:     100 Trying
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC628120381484FED9FBC7FE7D1 F341E8
To: <sip:269998@10.2.2.75>
From: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 3179 INVITE
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO1599-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:29.71
Type:         & nbsp;SIPIncoming
Description:     180 Ringing
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC628120381484FED9FBC7FE7D1 F341E8
To: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
From: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 3179 INVITE
Contact: <sip:269998@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1599-CPO00936
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:32.08
Type:         & nbsp;SIPIncoming
Description:     INVITE
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

INVITE sip:269997@172.26.253.176:5061;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-1
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Date: Tue, 23 Jan 2007 16:42:32 GMT
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32240 INVITE
Max-Forwards: 70
Contact: <sip:269997@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Type: application/sdp
Content-Length: 161

v=0
o=- 2134569223 1429926152 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 0.0.0.0
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000
a=ptime:20
a=sendonly


============================================================ =========
Time:         & nbsp;10:42:32.10
Type:         & nbsp;SIPOutgoing
Description:     100 Trying
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-1
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32240 INVITE
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:32.10
Type:         & nbsp;SIPOutgoing
Description:     200 OK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-1
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32240 INVITE
Content-Type: application/sdp
Content-Length: 342

v=0
o=- 633051457521054452 633051457521054470 IN IP4 172.26.253.176
s=WOSI SIP 0.5
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 0 8 3 98 7 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:7 LPC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



============================================================ =========
Time:         & nbsp;10:42:32.15
Type:         & nbsp;SIPIncoming
Description:     ACK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

ACK sip:269997@172.26.253.176:5061 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-2
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32240 ACK
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:32.90
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKC628120381484FED9FBC7FE7D1 F341E8
To: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
From: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 3179 INVITE
Contact: <sip:269998@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1599-CPO00936
Content-Type: application/sdp
Content-Length: 155

v=0
o=- 2137739189 862670773 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8330 RTP/AVP 18
a=rtpmap:18 G729/8000
a=sendrecv


============================================================ =========
Time:         & nbsp;10:42:32.90
Type:         & nbsp;SIPOutgoing
Description:     ACK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

ACK sip:269998@10.2.2.75:5060 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK6BA9E1E9D248427B9C0B04E301 40672A
From: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
To: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 3179 ACK
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:33.73
Type:         & nbsp;SIPOutgoing
Description:     REGISTER
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKDB4179E10BB14695AACB1F980E DA2316
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
To: "269997" <sip:269997@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4508 REGISTER
Expires: 1800
Allow: INVITE,ACK,CANCEL,REFER,BYE,NOTIFY,OPTIONS,INFO
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:42:33.76
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKDB4179E10BB14695AACB1F980E DA2316
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570553-co1636
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4508 REGISTER
Expires: 1800
Contact: <sip:269997@172.26.253.176:5061>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO1636-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:04.73
Type:         & nbsp;SIPOutgoing
Description:     REGISTER
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKE1DF11A6C766458AA8784412E5 A20AE6
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
To: "269997" <sip:269997@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4509 REGISTER
Expires: 1800
Allow: INVITE,ACK,CANCEL,REFER,BYE,NOTIFY,OPTIONS,INFO
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:04.76
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKE1DF11A6C766458AA8784412E5 A20AE6
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570584-co1908
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4509 REGISTER
Expires: 1800
Contact: <sip:269997@172.26.253.176:5061>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO1908-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:07.26
Type:         & nbsp;SIPIncoming
Description:     INVITE
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

INVITE sip:269997@172.26.253.176:5061;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-1
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51900 INVITE
Max-Forwards: 70
Contact: <sip:269997@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1599-CPO00936
Content-Type: application/sdp
Content-Length: 160

v=0
o=- 2137739189 862670774 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 0.0.0.0
t=0 0
m=audio 8330 RTP/AVP 18
a=rtpmap:18 G729/8000
a=ptime:20
a=sendonly


============================================================ =========
Time:         & nbsp;10:43:07.27
Type:         & nbsp;SIPOutgoing
Description:     100 Trying
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-1
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51900 INVITE
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:07.27
Type:         & nbsp;SIPOutgoing
Description:     200 OK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-1
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51900 INVITE
Content-Type: application/sdp
Content-Length: 342

v=0
o=- 633051457872777704 633051457872777722 IN IP4 172.26.253.176
s=WOSI SIP 0.5
c=IN IP4 172.26.253.176
t=0 0
m=audio 8000 RTP/AVP 18 0 8 3 98 7 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:7 LPC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



============================================================ =========
Time:         & nbsp;10:43:07.29
Type:         & nbsp;SIPIncoming
Description:     ACK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

ACK sip:269997@172.26.253.176:5061 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-2
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51900 ACK
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1599-CPO00936
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:07.93
Type:         & nbsp;SIPIncoming
Description:     INVITE
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

INVITE sip:269997@172.26.253.176:5061;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-3
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32250 INVITE
Max-Forwards: 70
Contact: <sip:269997@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Type: application/sdp
Content-Length: 168

v=0
o=- 2134569223 1429926153 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000
a=ptime:20
a=sendrecv


============================================================ =========
Time:         & nbsp;10:43:07.94
Type:         & nbsp;SIPOutgoing
Description:     100 Trying
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-3
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32250 INVITE
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:07.94
Type:         & nbsp;SIPOutgoing
Description:     200 OK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-3
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32250 INVITE
Content-Type: application/sdp
Content-Length: 342

v=0
o=- 633051457879496540 633051457879496558 IN IP4 172.26.253.176
s=WOSI SIP 0.5
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 0 8 3 98 7 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:7 LPC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



============================================================ =========
Time:         & nbsp;10:43:07.98
Type:         & nbsp;SIPIncoming
Description:     ACK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

ACK sip:269997@172.26.253.176:5061 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-4
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32250 ACK
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:13.77
Type:         & nbsp;SIPIncoming
Description:     BYE
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

BYE sip:269997@172.26.253.176:5061 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-5
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32260 BYE
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1428-CPO00795
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:13.77
Type:         & nbsp;SIPOutgoing
Description:     200 OK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-594-5
From: <sip:269999@10.2.2.75>;tag=t1169570532-co1428
To: "269997" <sip:269997@10.2.2.75>;tag=C631355965884BE690C568485FC 94934
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 32260 BYE
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:15.09
Type:         & nbsp;SIPIncoming
Description:     BYE
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

BYE sip:269997@172.26.253.176:5061 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-3
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51910 BYE
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2081-CO1599-CPO00936
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:15.10
Type:         & nbsp;SIPOutgoing
Description:     200 OK
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-63f-3
From: <sip:269998@10.2.2.75>;tag=t1169570549-co1599
To: "269997" <sip:269997@10.2.2.75>;tag=B3CBE5D3BA774C9AB5D652BD7D4 0DBD0
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 51910 BYE
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:35.74
Type:         & nbsp;SIPOutgoing
Description:     REGISTER
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK4CAE67999CE849FAB0CC262529 80CD48
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
To: "269997" <sip:269997@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4510 REGISTER
Expires: 1800
Allow: INVITE,ACK,CANCEL,REFER,BYE,NOTIFY,OPTIONS,INFO
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:43:35.77
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bK4CAE67999CE849FAB0CC262529 80CD48
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570615-co181
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4510 REGISTER
Expires: 1800
Contact: <sip:269997@172.26.253.176:5061>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO181-CPO00000
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:44:06.74
Type:         & nbsp;SIPOutgoing
Description:     REGISTER
From:         & nbsp;172.26.253.176
To:         &nb sp;10.2.2.75:5060
============================================================ =========

REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKEDF5191A521348E3B64A5BA1B6 98C8B2
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
To: "269997" <sip:269997@10.2.2.75>
Contact: <sip:269997@172.26.253.176:5061>
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4511 REGISTER
Expires: 1800
Allow: INVITE,ACK,CANCEL,REFER,BYE,NOTIFY,OPTIONS,INFO
User-Agent: WOSISIP 1.0
Max-Forwards: 70
Content-Length: 0



============================================================ =========
Time:         & nbsp;10:44:06.77
Type:         & nbsp;SIPIncoming
Description:     200 OK
From:         & nbsp;10.2.2.75:5060
To:         &nb sp;172.26.253.176
============================================================ =========

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5061;branch=z9hG4bKEDF5191A521348E3B64A5BA1B6 98C8B2
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570646-co442
From: "269997" <sip:269997@10.2.2.75>;tag=479D96477BD648FC939F6B56B8F 00EA5
Call-ID: 999A7AA43AD04E038C6A5038A4D586A6@172.26.253.176
CSeq: 4511 REGISTER
Expires: 1800
Contact: <sip:269997@172.26.253.176:5061>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2081-CO442-CPO00000
Content-Length: 0



LS SIP Messages
Code:

************* Log Opened (Jan 23 10:41:39) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199be170
From: <sip:269999@10.2.2.75>;tag=199c1bee
To: <sip:269999@10.2.2.75>
Call-Id: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218516 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:269999@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199be170
To: <sip:269999@10.2.2.75>;tag=t1169570504-co1185
From: <sip:269999@10.2.2.75>;tag=199c1bee
Call-ID: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218516 REGISTER
Expires: 3600
Contact: <sip:269999@172.26.253.176:5060>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP1989-CO1185-CPO00000
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (16 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199bed88
From: <sip:269998@10.2.2.75>;tag=199c069d
To: <sip:269998@10.2.2.75>
Call-Id: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218517 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:269998@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (31 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199bed88
To: <sip:269998@10.2.2.75>;tag=t1169570504-co1187
From: <sip:269998@10.2.2.75>;tag=199c069d
Call-ID: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218517 REGISTER
Expires: 3600
Contact: <sip:269998@172.26.253.176:5060>
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2035-CO1187-CPO00000
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (27625 Ms, From: 10.2.2.75:5060) <<<<
INVITE sip:269999@172.26.253.176:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-596-1
To: <sip:269999@172.26.253.176:5060>
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
Date: Tue, 23 Jan 2007 16:42:12 GMT
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21850 INVITE
Max-Forwards: 70
X-XLData: pc=924958;dnis=269999
Contact: <sip:269997@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP1989-CO1430-CPO00796
Content-Type: application/sdp
Content-Length: 308

v=0
o=- 2135486184 826863336 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 0 8 3 98 101
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (27672 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3ae4-596-1
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
To: <sip:269999@172.26.253.176:5060>
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21850 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3ae4-596-1
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
To: <sip:269999@172.26.253.176:5060>;tag=199c5c37
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21850 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (2531 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3ae4-596-1
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
To: <sip:269999@172.26.253.176>;tag=199c5c37
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21850 INVITE
Contact: <sip:269999@172.26.253.176:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 179
Content-Type: application/sdp

v=0
o=LanScape 3378559334 3378559334 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 172.26.253.176
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20


<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (2578 Ms, From: 10.2.2.75:5060) <<<<
ACK sip:269999@172.26.253.176:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63ae4-596-2
To: <sip:269999@172.26.253.176:5060>;tag=199c5c37
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21850 ACK
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP1989-CO1430-CPO00796
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (15032 Ms, From: 10.2.2.75:5060) <<<<
INVITE sip:269998@172.26.253.176:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-641-1
To: <sip:269998@172.26.253.176:5060>
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
Date: Tue, 23 Jan 2007 16:42:29 GMT
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54190 INVITE
Max-Forwards: 70
X-XLData: pc=925011;dnis=269998
Contact: <sip:269997@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2035-CO1601-CPO00937
Content-Type: application/sdp
Content-Length: 212

v=0
o=- 2145623418 1055104378 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8000 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (15078 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3af5-641-1
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
To: <sip:269998@172.26.253.176:5060>
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54190 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3af5-641-1
x-MyCustomHeader: "This is a modified transmitted SIP message."
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
To: <sip:269998@172.26.253.176:5060>;tag=199ca100
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54190 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (2344 Ms, To: 10.2.2.75:5060) >>>>
INVITE sip:269997@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199c622e
From: <sip:269999@172.26.253.176>;tag=199c5c37
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570532-co1430
Contact: <sip:269999@172.26.253.176:5060>
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21851 INVITE
Max-Forwards: 70
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 170
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Type: application/sdp

v=0
o=LanScape 429679109 429679109 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendonly
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (2468 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199c622e
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
From: <sip:269999@172.26.253.176:5060>;tag=199c5c37
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21851 INVITE
Contact: <sip:269999@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP1989-CO1430-CPO00796
Content-Type: application/sdp
Content-Length: 223

v=0
o=- 2135486184 826863337 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (109 Ms, To: 10.2.2.75:5060) >>>>
ACK sip:269999@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199c622e
From: <sip:269999@172.26.253.176>;tag=199c5c37
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570532-co1430
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21851 ACK
Max-Forwards: 70
Route: <sip:269999@10.2.2.75>
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (172 Ms, To: 10.2.2.75:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.2.2.75:5060;received=10.2.2.75;branch=z9hG4bK1a02024b45b6 3af5-641-1
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
To: <sip:269998@172.26.253.176>;tag=199ca100
Call-Id: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54190 INVITE
Contact: <sip:269999@172.26.253.176:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Length: 179
Content-Type: application/sdp

v=0
o=LanScape 3378559352 3378559352 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 172.26.253.176
t=0 0
m=audio 8330 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20


<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (203 Ms, From: 10.2.2.75:5060) <<<<
ACK sip:269999@172.26.253.176:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.2.75:5060;branch=z9hG4bK1a02024b45b63af5-641-2
To: <sip:269998@172.26.253.176:5060>;tag=199ca100
From: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54190 ACK
Max-Forwards: 70
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2035-CO1601-CPO00937
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (34922 Ms, To: 10.2.2.75:5060) >>>>
INVITE sip:269997@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d339b
From: <sip:269998@172.26.253.176>;tag=199ca100
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570549-co1601
Contact: <sip:269999@172.26.253.176:5060>
Call-Id: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54191 INVITE
Max-Forwards: 70
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 170
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Type: application/sdp

v=0
o=LanScape 429714296 429714296 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8330 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendonly
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (34954 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d339b
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
From: <sip:269998@172.26.253.176:5060>;tag=199ca100
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54191 INVITE
Contact: <sip:269998@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2035-CO1601-CPO00937
Content-Type: application/sdp
Content-Length: 224

v=0
o=- 2145623418 1055104379 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8000 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (63 Ms, To: 10.2.2.75:5060) >>>>
ACK sip:269998@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d339b
From: <sip:269998@172.26.253.176>;tag=199ca100
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570549-co1601
Call-Id: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54191 ACK
Max-Forwards: 70
Route: <sip:269998@10.2.2.75>
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (46 Ms, To: 10.2.2.75:5060) >>>>
INVITE sip:269997@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d04a4
From: <sip:269999@172.26.253.176>;tag=199c5c37
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570532-co1430
Contact: <sip:269999@172.26.253.176:5060>
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21852 INVITE
Max-Forwards: 70
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 177
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
Content-Type: application/sdp

v=0
o=LanScape 429714406 429714406 IN IP4 172.26.253.176
s=LanScape
c=IN IP4 172.26.253.176
t=0 0
m=audio 8222 RTP/AVP 18
a=rtpmap:18 G729/8000/1
a=sendrecv
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (671 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d04a4
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
From: <sip:269999@172.26.253.176:5060>;tag=199c5c37
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21852 INVITE
Contact: <sip:269999@10.2.2.75:5060>
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP1989-CO1430-CPO00796
Content-Type: application/sdp
Content-Length: 223

v=0
o=- 2135486184 826863338 IN IP4 10.2.2.75
s=ENS Session
c=IN IP4 172.26.253.176
t=0 0
m=audio 8002 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (625 Ms, To: 10.2.2.75:5060) >>>>
ACK sip:269999@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d04a4
From: <sip:269999@172.26.253.176>;tag=199c5c37
To: "269997" <sip:269997@10.2.2.75>;tag=t1169570532-co1430
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21852 ACK
Max-Forwards: 70
Route: <sip:269999@10.2.2.75>
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (5766 Ms, To: 10.2.2.75:5060) >>>>
BYE sip:269997@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d6c70
From: <sip:269999@172.26.253.176:5060>;tag=199c5c37
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
Call-Id: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21853 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (5782 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d6c70
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570532-co1430
From: <sip:269999@172.26.253.176:5060>;tag=199c5c37
Call-ID: 9686D9D8A8AE486BA30C6E4235E8E957@172.26.253.176
CSeq: 21853 BYE
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP1989-CO1430-CPO00796
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1313 Ms, To: 10.2.2.75:5060) >>>>
BYE sip:269997@10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d7191
From: <sip:269998@172.26.253.176:5060>;tag=199ca100
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
Call-Id: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54192 BYE
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (1328 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d7191
To: "269997" <sip:269997@10.2.2.75:5060>;tag=t1169570549-co1601
From: <sip:269998@172.26.253.176:5060>;tag=199ca100
Call-ID: F7C06F4BE2884A8496FE3068D611D9AD@172.26.253.176
CSeq: 54192 BYE
User-Agent: ENS2.2.102-IS1-RMRG3143-RG3143-EP2035-CO1601-CPO00937
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1359 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d577f
From: <sip:269999@10.2.2.75>;tag=199d0f85
To: <sip:269999@10.2.2.75>
Call-Id: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218518 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:269999@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (1375 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d577f
To: <sip:269999@10.2.2.75>;tag=t1169570596-co2
From: <sip:269999@10.2.2.75>;tag=199d0f85
Call-ID: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218518 REGISTER
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP1989-CO2-CPO00000
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (47 Ms, To: 10.2.2.75:5060) >>>>
REGISTER sip:10.2.2.75 SIP/2.0
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d770f
From: <sip:269998@10.2.2.75>;tag=199d2849
To: <sip:269998@10.2.2.75>
Call-Id: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218519 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:269998@172.26.253.176:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.7 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRx (31 Ms, From: 10.2.2.75:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.26.253.176:5060;rport;branch=z9hG4bK199d770f
To: <sip:269998@10.2.2.75>;tag=t1169570596-co4
From: <sip:269998@10.2.2.75>;tag=199d2849
Call-ID: c80a55e0-53a0-4e80-bab8-ffadfb8f0a3f-00000808@172.26.253.176
CSeq: 10218519 REGISTER
User-Agent: ENS2.2.102-IS1-RMRG0-RG3143-EP2035-CO4-CPO00000
Content-Length: 0




************* Log Closed (Jan 23 10:43:20) *************




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


Joined: June 14 2006
Location: United States
Posts: 142
Posted: January 23 2007 at 11:52am | IP Logged Quote mfitzgerald
Gee. . . should have proof read that one a little better. But I’m certain the point was indicated.
Back to Top View mfitzgerald's Profile Search for other posts by mfitzgerald Visit mfitzgerald's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: January 23 2007 at 12:29pm | IP Logged Quote support
Hi Fitz,

Thanks for the SIP logs. We will look at the problem as soon as we can.

I'm the same way about proof reading. Do it all the time and still make mistakes. We are golden as long as the point gets made :) 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: January 25 2007 at 10:09am | IP Logged Quote support
Hi Fitz,

We wanted to let you know that we did not forget about you. We are still working on this.

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


Joined: June 14 2006
Location: United States
Posts: 142
Posted: January 25 2007 at 10:13am | IP Logged Quote mfitzgerald
Thanks
Back to Top View mfitzgerald's Profile Search for other posts by mfitzgerald Visit mfitzgerald's Homepage
 
mfitzgerald
Vetran
Vetran


Joined: June 14 2006
Location: United States
Posts: 142
Posted: February 14 2007 at 11:29am | IP Logged Quote mfitzgerald
Hello.

Is there an update regarding this issue?
Back to Top View mfitzgerald's Profile Search for other posts by mfitzgerald Visit mfitzgerald's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: February 14 2007 at 1:26pm | IP Logged Quote support
Hey Fitz,

We are working on this right now - really, no kidding...    :)

Having the media engine call itself was not supported in the past. If I remember, there was a call leg issue that arose when having a multi line phone call itself. Not sure why the restriction is still there but we will try to remove it.

So for simplicity sake, if we allow a multi lined media engine to call itself, that would serve your application’s purpose???


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


Joined: June 14 2006
Location: United States
Posts: 142
Posted: February 14 2007 at 2:01pm | IP Logged Quote mfitzgerald
Glad to hear from you. I was starting to wonder. :)

Yes, a multi lined media engine able to call itself would be great.

Though we are not asking for a special development here.

It just seemed odd getting the results (in the above SIP Logs) time after time on something that appeared to be straight forward.

The limitation proved very inconvenient for the application I was working on.

I look forward to hearing the results on the removal of the limitation.

Thanks


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: February 14 2007 at 2:26pm | IP Logged Quote support
Fitz,

Do me a favor and answer the following question as simply as you can:

Why does your application require that the media engine call itself?

Give me a simple scenario if you can.

Support

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


Joined: June 14 2006
Location: United States
Posts: 142
Posted: February 14 2007 at 3:10pm | IP Logged Quote mfitzgerald
Our PBX vendor has a feature that automatically closes a queue if no agents are logged in. To prevent the queue closing during mass shift changes, etc. we were requested to write an application with two endpoints that would log in to the PBX. Each endpoint would belong to a separate queue. Since the endpoints would appear as agents to the PBX the queue would stay open. To prevent calls from being delivered to the pseudo-agents, the endpoints call each other.
Back to Top View mfitzgerald's Profile Search for other posts by mfitzgerald Visit mfitzgerald's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: February 14 2007 at 3:24pm | IP Logged Quote support
Ahhh...

That makes sense.

We will see if we can get the single instance of the media engine to do this. No guarantee though.

The other option would be to purchase another instance of the media engine and use two of them per application. You would then basically have one instance on port 5060 and the other on say port 5062. This dual solution would work out of the box. Something to think about for an immediate short term solution......

Using dual media engines per app would be cheaper than waisting a perfectly good second host computer per installation.


Suport
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: February 27 2007 at 6:27am | IP Logged Quote support
Hi Fitz,

We have performed the final review of why the media engine behaves as it does when calling itself. Due to an internal design decision, we do not allow the media engine to call itself. This has to do with the way he media engine handles call leg information and how it assigns incoming calls to available phone lines. We know what needs to be changed in order to allow the media engine to call itself but changing current functionality will have to wait until a later release. Hopefully we can perform the changes soon and get it in one of the upcoming releases this spring. We have added this feature request to the product road map because it is a useful capability that others may also require.

The best possible short term solution for an application to call itself will be to integrate dual media engines that operate on separate UDP SIP ports. In this way, the dual media engines will be totally isolated and allow the application to “call itself”.

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: June 21 2007 at 10:47am | IP Logged Quote support
Updated Note:

The latest release of the media engine now allows calling itself.

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