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: Notify Events Interface Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
hermes
Junior
Junior


Joined: October 27 2006
Posts: 64
Posted: May 30 2007 at 3:01am | IP Logged Quote hermes
Hello,

I need to use 'Notify Event Interface' to receive and send Notify Messages and I don´t understand very well how it works. Could you publish an example?

Thank you very much.
Back to Top View hermes's Profile Search for other posts by hermes
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 30 2007 at 8:36am | IP Logged Quote support
Hi hermes,

We are glad you are posting. We have not heard from you in a while and have been wondering how your VOIP development has progressed.

The SUBSCRIBE/NOTIFY event interface of the media engine is pretty simple. The basic model is this: For SIP devices to be able to receive NOTIFY events from the VOIP app (media engine), the SIP devices must SUBSCRIBE to those events offered by the VOIP app (media engine).

Another way to phrase this is:
For VOIP applications that want to offer events (i.e. fire NOTIFY events to other clients), the voip application must accept SUBSCRIBE SIP messages from other SIP devices.


The SUBSCRIBE/NOTIFY event interface can be best understood if we use an example.

Let us assume we have two VOIP applications that are based on the VOIP Media Engine. Assume one of them is a voicemail server and the other is a soft phone.

Now let’s say that the voicemail server has the ability to send to the soft phone indications when voicemail messages are waiting to be retrieved. In order for the voicemail server to know that a soft phone wants these event indications, the soft phone will have to tell the voicemail server that he wants notify events. The soft phone does this by SUBSCRIBing to any and all known events that are supported by the voicemail server.

Once SUBSCRIBE requests are received by the voicemail server, the voicemail server will send NOTIFY SIP messages to the soft phone whenever voicemail states change. In this case, a voicemail state change could be a new message waiting.

Next we will discuss a few SIP log examples of how the media engine SUBSCRIBE/NOTIFY mechanism works.


This SIP log is from a test application we use in our lab. For testing purposes, the application subscribes to its own event named “vphone-test-event-0”. Your VOIP applications can define whatever events exist – you are not limited. The header in the SUBSCRIBE SIP message you should notice is the “Event:” header. It contains the event name and an optional parameter. Both of these values your apps can define and agree upon.

For example, the Event header:
Event: vphone-test-event-0;param="Test Param"

In the SIP log below, the test app sends a SUBSCRIBE to itself through a LanScape SIP proxy.

The SUBSCRIBE is received by the test app and a “200 OK” is sent back through the proxy. The “200 OK” is routed back to the test app.

At this point the test app has basically subscribed to its own “vphone-test-event-0” event.


Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#3, 141 Ms, To: 192.168.1.2:5060) >>>>
SUBSCRIBE sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK0064eb88
From: <sip:333@ps>;tag=651aed
To: <sip:333@192.168.1.2:6060>
Call-Id: 30037b4b-49ad-415e-9e79-472d0749558f-00000ffc@192.168.1.2
CSeq: 6607604 SUBSCRIBE
Expires: 3600
Max-Forwards: 70
Contact: <sip:333@ps:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Test Param"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#3, 125 Ms, From: 192.168.1.2:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK0064eb88;received= 192.168.1.2
From: <sip:333@ps>;tag=651aed
To: <sip:333@192.168.1.2:6060>
Call-ID: 30037b4b-49ad-415e-9e79-472d0749558f-00000ffc@192.168.1.2
CSeq: 6607604 SUBSCRIBE
Proxy-Authenticate: Digest realm="ps", nonce="f55b954be7861acafdbf2acf0909782b", opaque="f99b17495877889addfd7ecd573e28f4"
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#4, 16 Ms, To: 192.168.1.2:5060) >>>>
SUBSCRIBE sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK00651046
From: <sip:333@ps>;tag=651dbb
To: <sip:333@192.168.1.2:6060>
Call-Id: d378bd8a-1c21-4e11-963c-9544810dbbd7-00000ffc@192.168.1.2
CSeq: 6634079 SUBSCRIBE
Expires: 3600
Max-Forwards: 70
Contact: <sip:333@ps:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5,nonce="f55b954be7861acafdbf2acf0909782b",opaqu e="f99b17495877889addfd7ecd573e28f4",realm="ps",response="b8 44b1c55c6bdc001cf0a56d47dcaf9b",uri="sip:333@192.168.1.2",us ername="guest"
Event: vphone-test-event-0;param="Test Param"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#4, 31 Ms, From: 192.168.1.2:5060) <<<<
SUBSCRIBE sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKfa2832db7f7ece309dccd0e6efe88 62c3.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK00651046;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: <sip:333@ps>;tag=651dbb
To: <sip:333@192.168.1.2:6060>
Call-ID: d378bd8a-1c21-4e11-963c-9544810dbbd7-00000ffc@192.168.1.2
CSeq: 6634079 SUBSCRIBE
Contact: <sip:333@ps:5060>
expires: 3600
max-forwards: 69
event: vphone-test-event-0;param="Test Param"
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#5, 15 Ms, To: 192.168.1.2:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKfa2832db7f7ece309dccd0e6efe88 62c3.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00651046
Record-Route: <sip:192.168.1.2>
From: <sip:333@ps>;tag=651dbb
To: <sip:333@192.168.1.2:6060>
Call-Id: d378bd8a-1c21-4e11-963c-9544810dbbd7-00000ffc@192.168.1.2
CSeq: 6634079 SUBSCRIBE
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#5, 0 Ms, From: 192.168.1.2:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00651046
Record-Route: <sip:192.168.1.2>
From: <sip:333@ps>;tag=651dbb
To: <sip:333@192.168.1.2:6060>
Call-ID: d378bd8a-1c21-4e11-963c-9544810dbbd7-00000ffc@192.168.1.2
CSeq: 6634079 SUBSCRIBE
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0




In this next section of SIP log, the test app sends a NOTIFY to itself. Remember, the test app has subscribed to its own event. The NOTIFY is send to the LanScape SIP proxy and then routed back to the test app.

Note the “Event:” SIP header in the NOTIFY. The header values can be controlled by your VOIP application to NOTIFY a subscribing app of specific event information. The “Event:” header can contain any information you need for your event.


Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#6, 24641 Ms, To: 192.168.1.2:5060) >>>>
NOTIFY sip:333@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK006549b9
From: <sip:333@ps>;tag=65536f
To: <sip:333@ps>
Call-Id: a2dbb6b8-99ff-4c8d-8cf1-2ec295995e53-00000ffc@192.168.1.2
CSeq: 6646431 NOTIFY
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:6060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="PII450"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#6, 24641 Ms, From: 192.168.1.2:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK006549b9;received= 192.168.1.2
From: <sip:333@ps>;tag=65536f
To: <sip:333@ps>
Call-ID: a2dbb6b8-99ff-4c8d-8cf1-2ec295995e53-00000ffc@192.168.1.2
CSeq: 6646431 NOTIFY
Proxy-Authenticate: Digest realm="ps", nonce="f55b954be7861acafdbf2acf0909782b", opaque="abbd30d9d77708d778685ff6c86ea8c2"
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#7, 62 Ms, To: 192.168.1.2:5060) >>>>
NOTIFY sip:333@ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK00658bf6
From: <sip:333@ps>;tag=65612c
To: <sip:333@ps>
Call-Id: 3d58bf0d-9e8e-4c23-ba0c-f29944b6217a-00000ffc@192.168.1.2
CSeq: 6655495 NOTIFY
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:6060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5,nonce="f55b954be7861acafdbf2acf0909782b",opaqu e="abbd30d9d77708d778685ff6c86ea8c2",realm="ps",response="fd c3194b49860cee282a2c5645afa59a",uri="sip:333@ps",username="g uest"
Event: vphone-test-event-0;param="PII450"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#7, 62 Ms, From: 192.168.1.2:5060) <<<<
NOTIFY sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf3193219c7c4341b4512b56f82e60 fe1c.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK00658bf6;received= 192.168.1.2
Record-Route: <sip:192.168.1.2:5060;lr>
From: <sip:333@ps>;tag=65612c
To: <sip:333@ps>
Call-ID: 3d58bf0d-9e8e-4c23-ba0c-f29944b6217a-00000ffc@192.168.1.2
CSeq: 6655495 NOTIFY
Contact: <sip:333@192.168.1.2:6060>
max-forwards: 69
event: vphone-test-event-0;param="PII450"
x-customheader-extension-333: "This is a modified transmitted SIP message."
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#8, 0 Ms, To: 192.168.1.2:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKf3193219c7c4341b4512b56f82e60 fe1c.0
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00658bf6
Record-Route: <sip:192.168.1.2>
From: <sip:333@ps>;tag=65612c
To: <sip:333@ps>
Call-Id: 3d58bf0d-9e8e-4c23-ba0c-f29944b6217a-00000ffc@192.168.1.2
CSeq: 6655495 NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#8, 0 Ms, From: 192.168.1.2:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:6060;received=192.168.1.2;rport=6060;branch=z9hG 4bK00658bf6
Record-Route: <sip:192.168.1.2>
From: <sip:333@ps>;tag=65612c
To: <sip:333@ps>
Call-ID: 3d58bf0d-9e8e-4c23-ba0c-f29944b6217a-00000ffc@192.168.1.2
CSeq: 6655495 NOTIFY
Server: LanScape Centrex Proxy/3.42.1.9 (www.LanScapeCorp.com)
Content-Length: 0




Once a VOIP app no longer wants to receive events from another VOIP app, it unSUBSCRIBEs from the event.

The explanation of the SUBSCRIBE/NOTIFY interface is more involved than it actually is. Remember that the media engine will handle all of the low level SIP details for you.

We do not have a code example that we can release. We are sorry for this. We will put this on our “to do” list.

Obtaining additional higher levels of support:
We are now offering paid support contracts to customers who want a higher level of direct access to our support staff and developers. We started this new support program at the beginning of 2007 to ensure our support and development efforts remain focused. We are incredibly busy here these days and every minute of development/support time is precious.

All free support we currently offer will take a back seat to customers who have a support contracts with us. Support contracts allow us to quickly respond to customer needs in addition to offering a higher level of support such as additional code samples and remote debugging and configuration of VOIP systems, etc. There are many other good benefits to paid support that will impact you. If you are interested in the details, please send an email to our support group. We will respond promptly and get you the information you need.

Thanks hermes!


Support

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


Joined: October 27 2006
Posts: 64
Posted: May 31 2007 at 2:30am | IP Logged Quote hermes
Thank you very much.

I´ve got another doubt. When a client calls StopEventSubscription procedure, how can my server detect it to close notify handle?

Thanks.
Back to Top View hermes's Profile Search for other posts by hermes
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: May 31 2007 at 9:05am | IP Logged Quote support
Hi hermes,

We will assume the client VOIP application and the server VOIP application are both using the VOIP Media Engine.

We will discuss the complete subscribe cycle between client and server.


Subscribing to events:
When a VOIP client calls the StartEventSubscription () API procedure, the client’s media engine will send a SUBSCRIBE SIP message to the server. This SIP message will have an “Event:” SIP header that contains event specific data. The SIP message will also contain an “Expires:” SIP header that contains a non-zero value. For example:

Code:

SUBSCRIBE sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK05a5bcf8
From: <sip:333@ps>;tag=5a5ec5d
To: <sip:333@192.168.1.2:6060>
Call-Id: 5032ea7a-8d11-459e-84e2-6c34b8868dbc-00001904@192.168.1.2
CSeq: 10855604 SUBSCRIBE
Expires: 3600
Max-Forwards: 70
Contact: <sip:333@ps:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Test Param"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



The server VOIP application must process the SipSubscriptionReceived immediate event. When this event is processed by the server, the server receives the address of a SUBSCRIBE_REQUEST structure. In the SUBSCRIBE_REQUEST structure, the server inspects the pEventName structure member to see if the event name string is supported. Note: The event names you select for your client/server events are totally up to you.

If the server wants to accept the SUBSCRIBE request it must take ownership of the NotifyHandle in the SUBSCRIBE_REQUEST structure. This handle must eventually be freed by the application using the CloseNotifyHandle() API procedure when the server no longer needs to send SIP NOTIFY events to the client. The server application then sets the AcceptRequest value in the SUBSCRIBE_REQUEST structure to tell the media engine that the application supports the SUBSCRIPTION. When control returns back to the media engine from the event callback handler, the media engine will send a “200 OK” response to the client. This tells the client that all is ok and the SUBSCRIBE was accepted by the server.



At this time, the server can use the stored NotifyHandle from above and send events to the client application. Events are sent to the client application in the form of SIP NOTIFY messages.


Unsubscribing to events:
At some time later, the client will no longer want to receive events from the server. The client calls the StopEventSubscription() API procdure to do this.

When the client calls the StopEventSubscription() API procedure, the client’s media engine will send another SUBSCRIBE request to the server. For example:

Code:

SUBSCRIBE sip:333@192.168.1.2:6060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK05a5f165
From: <sip:333@ps>;tag=5a5feda
To: <sip:333@192.168.1.2:6060>
Call-Id: f5bb58cd-9235-4d96-aaf5-9ff7c550b3fd-00001904@192.168.1.2
CSeq: 10886094 SUBSCRIBE
Expires: 0
Max-Forwards: 70
Contact: <sip:333@ps:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.31 (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Test Param"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0


This SUBSCRIBE SIP message contains the “Event:” SIP header that describes the event subscription. It also contains the “Expires:” SIP header with a value of zero. This indicates to the server that the client no longer wants to receive NOTIFY SIP messages for the event.

Because the server processes the SipSubscriptionReceived immediate event, the server application will again receive the address of the SUBSCRIBE_REQUEST structure. In this structure, the ExpiresSeconds value will be set to zero indicating the client’s desire to unsubscribe from the specified event.

The server application will set the AcceptRequest value in the SUBSCRIBE_REQUEST structure so that the media engine sends back to the client a “200 OK” response.

The server must now do 2 things to clean up:

It must call the CloseNotifyHandle() API procedure using the original handle the application saved when the event subscription was started.

AND

It must call the CloseNotifyHandle() API procedure using the NotifyHandle value from the “unsubscribe” SUBSCRIBE_REQUEST structure.


We hope this helps,



Support

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


Joined: October 27 2006
Posts: 64
Posted: May 31 2007 at 9:35am | IP Logged Quote hermes
I´ve already undestood it.

Thank you very much.
Back to Top View hermes's Profile Search for other posts by hermes
 
hermes
Junior
Junior


Joined: October 27 2006
Posts: 64
Posted: June 04 2007 at 4:16am | IP Logged Quote hermes
Hello,

I´ve been testing The SUBSCRIBE/NOTIFY event interface and it works very well, but I´ve got a problem.

When I call SendEventNotification function it normally returns SipSuccess, but it returns sometimes SipEventNotifyNotAccepted. If I recall three or four times SendEventNotification finally it works.

What is happening?

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 04 2007 at 8:10am | IP Logged Quote support
Hi hermes,

To determine the exact cause, we would have to see a Sip log from your media engine application that calls the SendEventNotification() API procedure.

There are two ways the media engine will send the SipEventNotifyNotAccepted event to your application:

1) If the receiving end of the NOTIFY challenges the NOTIFY (by responding with a 401 or 407) and your sending application has not been configured with the proper authentication information.

2) If the receiving end of the NOTIFY responds with some other error code response.

Please post your log file if you want. We will take a look at it.

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


Joined: October 27 2006
Posts: 64
Posted: June 04 2007 at 9:36am | IP Logged Quote hermes
Hello,

this is the log.

Code:

************* Log Opened (Jun 04 16:31:25) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a1742
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=205a5a7 f
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: ef0f5873-f748-46cf-ae5a-dd66f7d6e5de-00001754@192.168.1.43
CSeq: 5914517 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK205a1742;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=205a5a7 f
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-ID: ef0f5873-f748-46cf-ae5a-dd66f7d6e5de-00001754@192.168.1.43
CSeq: 5914517 REGISTER
WWW-Authenticate: Digest realm="vocalia", nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2b57bbee71adf07dcb11b0dbcc9890e2"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a494f
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=205a0a5 1
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: ef0f5873-f748-46cf-ae5a-dd66f7d6e5de-00001754@192.168.1.43
CSeq: 5914518 REGISTER
Authorization: Digest algorithm=md5, nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2b57bbee71adf07dcb11b0dbcc9890e2", realm="vocalia", response="5797f549fbd8d618a0f4c45b3c7f2134", uri="sip:84.77.115.172", username="SipMediaRecognition1DS"
Expires: 3600
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (15 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK205a494f;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=205a0a5 1
To: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=41
Call-ID: ef0f5873-f748-46cf-ae5a-dd66f7d6e5de-00001754@192.168.1.43
CSeq: 5914518 REGISTER
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>;expires =3600
Expires: 3600
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (13641 Ms, From: 192.168.1.25:5060) <<<<
INVITE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf15500e7d85211977416a830d942 0967c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK04a3d1a5;received= 192.168.1.2;wanip=84.77.115.172
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728867 INVITE
Contact: <sip:2@192.168.1.2:5060>
max-forwards: 69
organization: 07DBE170-ED9E-40B4-9410-6C7064FF009C
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   225

v=0
o=2 77837250 77837250 IN IP4 192.168.1.25
s=LanScape
c=IN IP4 192.168.1.25
t=0 0
m=audio 9001 RTP/AVP 125 101
a=rtpmap:125 PCM/11050/1
a=rtpmap:101 telephone-event/11050/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (13672 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf15500 e7d85211977416a830d9420967c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a3d1a5
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728867 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf15500 e7d85211977416a830d9420967c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a3d1a5
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS;tag=205a8688
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728867 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (500 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf15500 e7d85211977416a830d9420967c.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a3d1a5
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=205a868 8;x-original-dest=SipMediaRecognition1DS
Call-Id: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728867 INVITE
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 177
Content-Type: application/sdp

v=0
o=LanScape 3389956299 3389956299 IN IP4 192.168.1.43
s=LanScape
c=IN IP4 192.168.1.43
t=0 0
m=audio 9000 RTP/AVP 125
a=rtpmap:125 PCM/11050/1
a=sendrecv
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (531 Ms, From: 192.168.1.25:5060) <<<<
ACK sip:SipMediaRecognition1DS@84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKl15500e7d85211977416a830d942 0967c
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a3d1a5
Route: <sip:SipMediaRecognition1DS@192.168.1.43>
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=205a868 8;x-original-dest=SipMediaRecognition1DS
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728867 ACK
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1016 Ms, From: 192.168.1.25:5060) <<<<
SUBSCRIBE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKfa656c2e95b3e7e34019ea5a6e33 93322.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK04a3f738;received= 192.168.1.2;wanip=84.77.115.172
From: <sip:2@192.168.1.25>;tag=4a404ad
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: 65e8e587-e07c-47e0-9c32-0a2a323f7053-00000508@192.168.1.2
CSeq: 10756497 SUBSCRIBE
Contact: <sip:2@192.168.1.25:5060>
expires: 4294966
max-forwards: 69
event: Adaptation Result
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1031 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKfa656c2e95b3e7e34019ea5a6e33 93322.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a3f738
From: <sip:2@192.168.1.25>;tag=4a404ad
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-Id: 65e8e587-e07c-47e0-9c32-0a2a323f7053-00000508@192.168.1.2
CSeq: 10756497 SUBSCRIBE
Event: Adaptation Result
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (4078 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:2@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a6d0c
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9c71
To: <sip:2@192.168.1.25>
Call-Id: add0f3d3-2f19-4dab-9281-363589fccc00-00001754@192.168.1.43
CSeq: 5920376 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (4078 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK205a6d0c;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9c71
To: <sip:2@192.168.1.25>
Call-ID: add0f3d3-2f19-4dab-9281-363589fccc00-00001754@192.168.1.43
CSeq: 5920376 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2ea3ba9fb3b0987100198488ea59b6a5"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (62 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:2@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a91f8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9f6d
To: <sip:2@192.168.1.25>
Call-Id: 9ecc3a67-979e-4f3f-a912-08f24d36c87e-00001754@192.168.1.43
CSeq: 5946897 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2ea3ba9fb3b0987100198488ea59b6a5", realm="vocalia", response="a12189f8f7393609c90909a7fedda14b", uri="sip:2@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (62 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK205a91f8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9f6d
To: <sip:2@192.168.1.25>
Call-ID: 9ecc3a67-979e-4f3f-a912-08f24d36c87e-00001754@192.168.1.43
CSeq: 5946897 NOTIFY
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (69485 Ms, From: 192.168.1.25:5060) <<<<
BYE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf979b45b516a479e72d97f9884f7 b9082.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK04a500e6;received= 192.168.1.2;wanip=84.77.115.172
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=205a868 8;x-original-dest=SipMediaRecognition1DS
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728869 BYE
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (69485 Ms, To: 192.168.1.2:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf979b4 5b516a479e72d97f9884f7b9082.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a500e6
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=205a868 8;x-original-dest=SipMediaRecognition1DS
Call-Id: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728869 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1500 Ms, From: 192.168.1.25:5060) <<<<
BYE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf979b45b516a479e72d97f9884f7 b9082.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK04a500e6;received= 192.168.1.2;wanip=84.77.115.172
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=205a868 8;x-original-dest=SipMediaRecognition1DS
Call-ID: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728869 BYE
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1500 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 481 Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf979b4 5b516a479e72d97f9884f7b9082.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK04a500e6
From: 2 <sip:2@84.77.115.172>;tag=4a3be31
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=6de3050 0;x-original-dest=SipMediaRecognition1DS
Call-Id: 69583b76-dc93-436b-a864-07cce143a859-00000508@192.168.1.2
CSeq: 10728869 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 04 2007 at 10:11am | IP Logged Quote support
Hi hermes,

Are you saying that the SIP log you just posted is from a test that generated the SipEventNotifyNotAccepted event?

We ask this because the SIP log gives no indication of errors.


The portion of the SIP log we are interested in is:

Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (62 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:2@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a91f8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9f6d
To: <sip:2@192.168.1.25>
Call-Id: 9ecc3a67-979e-4f3f-a912-08f24d36c87e-00001754@192.168.1.43
CSeq: 5946897 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2ea3ba9fb3b0987100198488ea59b6a5", realm="vocalia", response="a12189f8f7393609c90909a7fedda14b", uri="sip:2@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (62 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK205a91f8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9f6d
To: <sip:2@192.168.1.25>
Call-ID: 9ecc3a67-979e-4f3f-a912-08f24d36c87e-00001754@192.168.1.43
CSeq: 5946897 NOTIFY
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0



… and it looks normal.

What we have to do is see a non “200 OK” response for the NOTIFY coming back to your application via the proxy. Either authentication retries are triggering the error event or a real SIP error response is being returned from the UA that received the NOTIFY. Keep logging until you get the SipEventNotifyNotAccepted event and then look at your SIP log to see if a SIP response to the NOTIFY was something other than a 200.

Another thing to try: To make sure that authentication is not triggering this situation, try your tests with authentication off or at least turn the “Nonce expire time” to a huge values. See the main menu Configure->Authentication settings on your LanScape SIP proxy.

Repost as needed,


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


Joined: October 27 2006
Posts: 64
Posted: June 04 2007 at 10:54am | IP Logged Quote hermes
In this log appears:

Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (4078 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:2@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK205a6d0c
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9c71
To: <sip:2@192.168.1.25>
Call-Id: add0f3d3-2f19-4dab-9281-363589fccc00-00001754@192.168.1.43
CSeq: 5920376 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (4078 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK205a6d0c;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=205a9c71
To: <sip:2@192.168.1.25>
Call-ID: add0f3d3-2f19-4dab-9281-363589fccc00-00001754@192.168.1.43
CSeq: 5920376 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="6272c3d291c14ed96ca3acbce70d3f56", opaque="2ea3ba9fb3b0987100198488ea59b6a5"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0



Thanks
Back to Top View hermes's Profile Search for other posts by hermes
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 04 2007 at 11:26am | IP Logged Quote support
hermes,

Very good work. This says that authentication retries are triggering the SipEventNotifyNotAccepted event being sent to your application.

Do us a favor - please email us the complete log from this latest test run. We need to see why authentications are being "retried too many times". Please send the complete log to support 'at' lanscapecorp.com

If authentications are triggering the event, all your application has to do is retry the notification and it will then succeed.

We will wait for your entire SIP log. Good work.


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


Joined: October 27 2006
Posts: 64
Posted: June 05 2007 at 2:29am | IP Logged Quote hermes
Here is one more log:

Code:

************* Log Opened (Jun 05 09:01:19) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e48345
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e469e 1
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974745 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e48345;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e469e 1
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-ID: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974745 REGISTER
WWW-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="154832b019a2fdebe145568edb30b2ac"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e4c8de
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e48d1 5
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974746 REGISTER
Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="154832b019a2fdebe145568edb30b2ac", realm="vocalia", response="aae938bfa1f306cd3a1eaa9c4cfaa3e2", uri="sip:84.77.115.172", username="SipMediaRecognition1DS"
Expires: 3600
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (15 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e4c8de;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e48d1 5
To: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=41
Call-ID: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974746 REGISTER
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>;expires =3600
Expires: 3600
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (11313 Ms, From: 192.168.1.25:5060) <<<<
INVITE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf5438e0d295295bbf2677fb826df fd5b8.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK082e4157;received= 192.168.1.2;wanip=84.77.115.172
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028686 INVITE
Contact: <sip:1@192.168.1.2:5060>
max-forwards: 69
organization: 07DBE170-ED9E-40B4-9410-6C7064FF009C
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length:   227

v=0
o=1 137229796 137229796 IN IP4 192.168.1.25
s=LanScape
c=IN IP4 192.168.1.25
t=0 0
m=audio 9001 RTP/AVP 125 101
a=rtpmap:125 PCM/11050/1
a=rtpmap:101 telephone-event/11050/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-15



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (11343 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf5438e 0d295295bbf2677fb826dffd5b8.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e4157
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028686 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf5438e 0d295295bbf2677fb826dffd5b8.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e4157
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS;tag=23e4c7df
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028686 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0





>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (500 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf5438e 0d295295bbf2677fb826dffd5b8.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e4157
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=23e4c7d f;x-original-dest=SipMediaRecognition1DS
Call-Id: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028686 INVITE
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 177
Content-Type: application/sdp

v=0
o=LanScape 3390015692 3390015692 IN IP4 192.168.1.43
s=LanScape
c=IN IP4 192.168.1.43
t=0 0
m=audio 9000 RTP/AVP 125
a=rtpmap:125 PCM/11050/1
a=sendrecv
a=ptime:20



<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (531 Ms, From: 192.168.1.25:5060) <<<<
ACK sip:SipMediaRecognition1DS@84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKl5438e0d295295bbf2677fb826df fd5b8
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e4157
Route: <sip:SipMediaRecognition1DS@192.168.1.43>
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=23e4c7d f;x-original-dest=SipMediaRecognition1DS
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028686 ACK
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1016 Ms, From: 192.168.1.25:5060) <<<<
SUBSCRIBE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf4e68a5d5fe4709184db72c2c5b9 243d7.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK082e395b;received= 192.168.1.2;wanip=84.77.115.172
From: <sip:1@192.168.1.25>;tag=82e46d0
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-ID: a77beb06-9e32-4818-8a05-47cbae8ab7f3-00000494@192.168.1.2
CSeq: 3040244 SUBSCRIBE
Contact: <sip:1@192.168.1.25:5060>
expires: 4294966
max-forwards: 69
event: Adaptation Result
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1032 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf4e68a5d5fe4709184db72c2c5b9 243d7.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e395b
From: <sip:1@192.168.1.25>;tag=82e46d0
To: <sip:sipmediarecognition1ds@84.77.115.172>;x-original- dest=SipMediaRecognition1DS
Call-Id: a77beb06-9e32-4818-8a05-47cbae8ab7f3-00000494@192.168.1.2
CSeq: 3040244 SUBSCRIBE
Event: Adaptation Result
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (4453 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e4afdb
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4df40
To: <sip:1@192.168.1.25>
Call-Id: 9e069f1e-2cff-464b-a73c-5176c29ed1e8-00000478@192.168.1.43
CSeq: 14981495 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (4453 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e4afdb;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4df40
To: <sip:1@192.168.1.25>
Call-ID: 9e069f1e-2cff-464b-a73c-5176c29ed1e8-00000478@192.168.1.43
CSeq: 14981495 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="94d2ea3aa122534879b0dbe44f93b84b"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (47 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e4d4b8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4e22d
To: <sip:1@192.168.1.25>
Call-Id: 1123c8d7-157c-4384-9025-a128e6613805-00000478@192.168.1.43
CSeq: 15008001 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="94d2ea3aa122534879b0dbe44f93b84b", realm="vocalia", response="684e6e6d7ddd6ae748a71a4e9953de9b", uri="sip:1@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="true#Quisiéramos que leyera este texto en voz alta para que el sistema pueda acostumbrarse a su voz."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (47 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK23e4d4b8
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4e22d
To: <sip:1@192.168.1.25>
Call-ID: 1123c8d7-157c-4384-9025-a128e6613805-00000478@192.168.1.43
CSeq: 15008001 NOTIFY
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (4015 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e5104d
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e519a9
To: <sip:1@192.168.1.25>
Call-Id: b96fc145-d68f-4136-8f8a-0e17602735df-00000478@192.168.1.43
CSeq: 14996994 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="false#"
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (4015 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e5104d;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e519a9
To: <sip:1@192.168.1.25>
Call-ID: b96fc145-d68f-4136-8f8a-0e17602735df-00000478@192.168.1.43
CSeq: 14996994 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="2ba56aecbb8bd783943714c6a689fe5f"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (47 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e5151b
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4bd73
To: <sip:1@192.168.1.25>
Call-Id: a62258d3-2990-4b8e-9ccc-10d175e1a358-00000478@192.168.1.43
CSeq: 15010027 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="2ba56aecbb8bd783943714c6a689fe5f", realm="vocalia", response="684e6e6d7ddd6ae748a71a4e9953de9b", uri="sip:1@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="false#"
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (63 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK23e5151b
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4bd73
To: <sip:1@192.168.1.25>
Call-ID: a62258d3-2990-4b8e-9ccc-10d175e1a358-00000478@192.168.1.43
CSeq: 15010027 NOTIFY
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (2719 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e4ca87
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4f9ec
To: <sip:1@192.168.1.25>
Call-Id: b62934e2-b66d-4dcb-a019-89e97912ed61-00000478@192.168.1.43
CSeq: 14988323 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="true#Cuando haya terminado de leer, haremos algunos ajustes tras los cuales podrá comenzar a dictar."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (2703 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e4ca87;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4f9ec
To: <sip:1@192.168.1.25>
Call-ID: b62934e2-b66d-4dcb-a019-89e97912ed61-00000478@192.168.1.43
CSeq: 14988323 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="a434c74999438459b100cdc2dcae3311"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (62 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e4ef73
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4fce8
To: <sip:1@192.168.1.25>
Call-Id: d51f5a1b-476e-46cb-b1ba-f8d57528e72d-00000478@192.168.1.43
CSeq: 15014844 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="a434c74999438459b100cdc2dcae3311", realm="vocalia", response="684e6e6d7ddd6ae748a71a4e9953de9b", uri="sip:1@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="true#Cuando haya terminado de leer, haremos algunos ajustes tras los cuales podrá comenzar a dictar."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (62 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 481 Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK23e4ef73
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4fce8
To: <sip:1@192.168.1.25>;tag=e57c0000
Call-ID: d51f5a1b-476e-46cb-b1ba-f8d57528e72d-00000478@192.168.1.43
CSeq: 15014844 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="a434c74999438459b100cdc2dcae3311"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (2141 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e523b6
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e52d12
To: <sip:1@192.168.1.25>
Call-Id: 8ab6af5a-d856-4f0f-9c30-1c8ef2a69267-00000478@192.168.1.43
CSeq: 15001963 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Event: Adaptation Result;param="true#El texto que va a leer explica algunas de las razones por las que hablarle a su PC no es igual que hablarle a una persona."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (2157 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e523b6;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e52d12
To: <sip:1@192.168.1.25>
Call-ID: 8ab6af5a-d856-4f0f-9c30-1c8ef2a69267-00000478@192.168.1.43
CSeq: 15001963 NOTIFY
Proxy-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="315199e1a48de02f3d1062161907b154"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (62 Ms, To: 192.168.1.25:5060) >>>>
NOTIFY sip:1@192.168.1.25 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e52893
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4d0eb
To: <sip:1@192.168.1.25>
Call-Id: 1cb67dab-eb13-469e-a2e6-4259745b70c0-00000478@192.168.1.43
CSeq: 15015011 NOTIFY
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Proxy-Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="315199e1a48de02f3d1062161907b154", realm="vocalia", response="684e6e6d7ddd6ae748a71a4e9953de9b", uri="sip:1@192.168.1.25", username="SipMediaRecognition1DS"
Event: Adaptation Result;param="true#El texto que va a leer explica algunas de las razones por las que hablarle a su PC no es igual que hablarle a una persona."
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (46 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;received=192.168.1.43;rport=5060;branch=z9 hG4bK23e52893
From: <sip:SipMediaRecognition1DS@192.168.1.25>;tag=23e4d0eb
To: <sip:1@192.168.1.25>
Call-ID: 1cb67dab-eb13-469e-a2e6-4259745b70c0-00000478@192.168.1.43
CSeq: 15015011 NOTIFY
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (3563 Ms, From: 192.168.1.25:5060) <<<<
BYE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf88401ccaf52930b91731561f219 2b031.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK082e9b20;received= 192.168.1.2;wanip=84.77.115.172
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=23e4c7d f;x-original-dest=SipMediaRecognition1DS
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028688 BYE
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (3563 Ms, To: 192.168.1.2:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf88401 ccaf52930b91731561f2192b031.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e9b20
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=23e4c7d f;x-original-dest=SipMediaRecognition1DS
Call-Id: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028688 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1500 Ms, From: 192.168.1.25:5060) <<<<
BYE sip:sipmediarecognition1ds@192.168.1.43:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.25:5060;branch=z9hG4bKf88401ccaf52930b91731561f219 2b031.0
Via: SIP/2.0/UDP 192.168.1.2:5060;rport=5060;branch=z9hG4bK082e9b20;received= 192.168.1.2;wanip=84.77.115.172
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=23e4c7d f;x-original-dest=SipMediaRecognition1DS
Call-ID: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028688 BYE
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1500 Ms, To: 192.168.1.25:5060) >>>>
SIP/2.0 481 Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.25:5060;received=192.168.1.25;branch=z9hG4bKf88401 ccaf52930b91731561f2192b031.0
Via: SIP/2.0/UDP 192.168.1.2:5060;received=192.168.1.2;rport=5060;branch=z9hG 4bK082e9b20
From: 1 <sip:1@84.77.115.172>;tag=82e6897
To: <sip:sipmediarecognition1ds@84.77.115.172>;tag=5b3d0a0 0;x-original-dest=SipMediaRecognition1DS
Call-Id: a7d8b59a-8df3-44bd-b5b6-ca83e020b946-00000494@192.168.1.2
CSeq: 3028688 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (1312 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e51b9d
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e4d3a 3
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974747 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (1312 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e51b9d;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e4d3a 3
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-ID: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974747 REGISTER
WWW-Authenticate: Digest realm="vocalia", nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="e8231f69c2f6ac50793a8dac072b8d67"
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.25:5060) >>>>
REGISTER sip:84.77.115.172 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bK23e53b0d
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e4ec4 7
To: <sip:SipMediaRecognition1DS@84.77.115.172>
Call-Id: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974748 REGISTER
Authorization: Digest algorithm=md5, nonce="16ee3f3183f344b2bec21a9fc95e7ed1", opaque="e8231f69c2f6ac50793a8dac072b8d67", realm="vocalia", response="aae938bfa1f306cd3a1eaa9c4cfaa3e2", uri="sip:84.77.115.172", username="SipMediaRecognition1DS"
Expires: 0
Max-Forwards: 70
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>
User-Agent: LanScape VOIP Media Engine/5.12.3.10 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 192.168.1.25:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;branch=z9hG4bK23e53b0d;received =192.168.1.43;wanip=84.77.115.172
From: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=23e4ec4 7
To: <sip:SipMediaRecognition1DS@84.77.115.172>;tag=26500
Call-ID: 5a452df0-924d-46b5-bb62-814edaf08841-00000478@192.168.1.43
CSeq: 14974748 REGISTER
Contact: <sip:SipMediaRecognition1DS@192.168.1.43:5060>;expires =0
Expires: 0
Server: LanScape Centrex Proxy/3.42.0.2 (www.LanScapeCorp.com)
Content-Length: 0




************* Log Closed (Jun 05 09:01:53) *************




You can see four NOTIFY messages. One of these messages replies with a "481 Transaction Does Not Exist" error.

What is happening?

Thank you very much for your support.
Back to Top View hermes's Profile Search for other posts by hermes
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 05 2007 at 8:41am | IP Logged Quote support
Hi hermes,

Thanks for the SIP log.

Authorization retries are not triggering the error.

We just briefly looked at your SIP log. This may be a long shot but… the only big difference that stands out that we can see from the SIP log is:

In the third NOTIFY message that gets sent out from your server to the client, the “Event:” header has a parameter string. In this string there is a comma character after the word “leer”.


Code:


Event: Adaptation Result;param="true#Cuando haya terminado de leer, haremos algunos ajustes tras los cuales podrá comenzar a dictar."



Try removing this comma and retest. Let us know what your new results are.

If this comma is causing the issue, then there may be a mild parse bug in the media engine. If this is the case, simply encode the parameter string using base64 encoding or some other text based encoding to hide the punctuation and to work around the bug.

We will wait for your response.


Support

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


Joined: October 27 2006
Posts: 64
Posted: June 05 2007 at 9:46am | IP Logged Quote hermes
Thank you very much!

I was being crazy with it. I´ve removed the comma and it works fine.

Thanks.
Back to Top View hermes's Profile Search for other posts by hermes
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 05 2007 at 10:07am | IP Logged Quote support

hermes,

Good work. We will investigate the parsing problem and fix this issue for a later release.

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