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

LanScape VOIP Media Engine™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: Problem registering with 3CX PBX Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
Jalal
Vetran
Vetran


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: April 08 2007 at 9:37am | IP Logged Quote Jalal
It seems Media Engine does not care about "407 Proxy Authentication Required" SIP message.

We tested 3CX IP PBX with Phoner Free softphone. Following is the log captured by a sniffer. IP PBX is installed on 10.10.10.14 and soft phone is installed on 10.10.10.15 .

Code:
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.10.10.14:5060) >>>>

REGISTER sip:10.10.10.14 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15;branch=z9hG4bK007a439423e4db11861976fc20524153
From: 127 <sip:127@10.10.10.14>;tag=27646
To: <sip:127@10.10.10.14>
Call-ID: 80E3AA93-23E4-DB11-8619-76FC20524153@10.10.10.15
CSeq: 1 REGISTER
Contact: <sip:127@10.10.10.15>
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 900
Content-Length: 0

<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 10.10.10.14:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.10.10.15;branch=z9hG4bK007a439423e4db11861976fc20524153
Proxy-Authenticate: Digest nonce="12820499140:c6b0e1f5013a64eeabfee7744a146a7a",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:127@10.10.10.14>;tag=8f47e635
From: "127"<sip:127@10.10.10.14>;tag=27646
Call-ID: 80E3AA93-23E4-DB11-8619-76FC20524153@10.10.10.15
CSeq: 1 REGISTER
Content-Length: 0

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 10.10.10.14:5060) >>>>
REGISTER sip:10.10.10.14 SIP/2.0
Via: SIP/2.0/UDP 10.10.10.15;branch=z9hG4bK8010dc9423e4db11861976fc20524153
From: 127 <sip:127@10.10.10.14>;tag=18225
To: <sip:127@10.10.10.14>
Call-ID: 80E3AA93-23E4-DB11-8619-76FC20524153@10.10.10.15
CSeq: 2 REGISTER
Contact: <sip:127@10.10.10.15>
Proxy-Authorization: Digest username="127", realm="3CXPhoneSystem", nonce="12820499140:c6b0e1f5013a64eeabfee7744a146a7a", uri="sip:10.10.10.14", response="efb44112bc9c2dd6a0284d9fafd5f543", algorithm=MD5
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 900
Content-Length: 0

<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 10.10.10.14:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.10.15;branch=z9hG4bK8010dc9423e4db11861976fc20524153
Contact: <sip:127@10.10.10.14:5062>;expires=52
Contact: <sip:127@10.10.10.15>;expires=900
To: <sip:127@10.10.10.14>;tag=ab1f2d2e
From: "127"<sip:127@10.10.10.14>;tag=18225
Call-ID: 80E3AA93-23E4-DB11-8619-76FC20524153@10.10.10.15
CSeq: 2 REGISTER
Content-Length: 0




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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 19 2007 at 2:14pm | IP Logged Quote support
Hi Jalal,

We accessed your 3CX pbx at your location from our lab. Thanks for getting that system set up for us.

Note: The IP addresses of your 3CX pbx server have been changed in this post for security reasons.


We located the REGISTER problem. Normally a SIP server or registrar server will challenge a REGISTER operation with a “401 Unauthorized” response as per the SIP RFC. For example, here is the LanScape Centrex Proxy:

Code:


************* Log Opened (Apr 19 13:45:04) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#7, 38625 Ms, To: 192.168.1.2:5060) >>>>
REGISTER sip:ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK07786614
From: <sip:333@ps>;tag=7786fd6
To: <sip:333@ps>
Call-Id: 60ba6b18-3f72-4fb7-a62c-c5979e3a35ef-000023e4@192.168.1.2
CSeq: 7620237 REGISTER
Expires: 36000
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:6060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#7, 38625 Ms, From: 192.168.1.2:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:6060;rport=6060;branch=z9hG4bK07786614;received= 192.168.1.2
From: <sip:333@ps>;tag=7786fd6
To: <sip:333@ps>
Call-ID: 60ba6b18-3f72-4fb7-a62c-c5979e3a35ef-000023e4@192.168.1.2
CSeq: 7620237 REGISTER
WWW-Authenticate: Digest realm="ps", nonce="68cbed355d8b7d37bbd4e14108c3488e", opaque="8bd88b4ad15e1cf817d36ae883a4c8ad"
Server: LanScape Centrex Proxy/3.42.1.7 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#8, 0 Ms, To: 192.168.1.2:5060) >>>>
REGISTER sip:ps SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:6060;rport;branch=z9hG4bK07787475
From: <sip:333@ps>;tag=7781ccd
To: <sip:333@ps>
Call-Id: 60ba6b18-3f72-4fb7-a62c-c5979e3a35ef-000023e4@192.168.1.2
CSeq: 7620238 REGISTER
Authorization: Digest algorithm=md5, nonce="68cbed355d8b7d37bbd4e14108c3488e", opaque="8bd88b4ad15e1cf817d36ae883a4c8ad", realm="ps", response="8165afb393fe703fcf8606e2e8c49a87", uri="sip:ps", username="guest"
Expires: 36000
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:6060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
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;rport=6060;branch=z9hG4bK07787475;received= 192.168.1.2
From: <sip:333@ps>;tag=7781ccd
To: <sip:333@ps>;tag=26500
Call-ID: 60ba6b18-3f72-4fb7-a62c-c5979e3a35ef-000023e4@192.168.1.2
CSeq: 7620238 REGISTER
Contact: <sip:333@192.168.1.2:6060>;user=phone;expires=36000
Expires: 36000
Server: LanScape Centrex Proxy/3.42.1.7 (www.LanScapeCorp.com)
Content-Length: 0

************* Log Closed (Apr 19 13:45:18) *************



The problem with the registrations when using the 3CX pbx is that it challenges the REGISTER using the “407 Proxy Authentication Required” response. The media engine simply ignores this 407 response because it expects a 401 response as per SIP RFC 3261:

From the RFC:

Code:

21.4.2 401 Unauthorized

   The request requires user authentication. This response is issued by
   UASs and registrars, while 407 (Proxy Authentication Required) is
   used by proxy servers.


All REGISTER operations of a registrar should be challenged using 401 responses.


What we have done is allow the media engine to now respond to register challenges when it received the 401 OR the 407 challenge responses. This should keep us out of trouble in the future. Here is a SIP log of us registering with your server:

Code:

************* Log Opened (Apr 19 13:49:13) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#1, 0 Ms, To: 187.107.63.63:5060) >>>>
REGISTER sip:187.107.63.63 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5090;rport;branch=z9hG4bK077c0df2
From: <sip:101@187.107.63.63>;tag=77c0a84
To: <sip:101@187.107.63.63>
Call-Id: 22a68057-3d80-4e4f-aa5d-9eb0ae4a1120-0000231c@192.168.1.2
CSeq: 8135781 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:101@192.168.1.2:5090>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-101: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#1, 0 Ms, From: 187.107.63.63:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5090;rport=5090;branch=z9hG4bK077c0df2;received= 75.73.79.80
Proxy-Authenticate: Digest nonce="12821481978:8d8b60e9217f51bf5ff10ddc71c78efc",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:101@187.107.63.63>;tag=f25c8849
From: <sip:101@187.107.63.63>;tag=77c0a84
Call-ID: 22a68057-3d80-4e4f-aa5d-9eb0ae4a1120-0000231c@192.168.1.2
CSeq: 8135781 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#2, 547 Ms, To: 187.107.63.63:5060) >>>>
REGISTER sip:187.107.63.63 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5090;rport;branch=z9hG4bK077c502e
From: <sip:101@187.107.63.63>;tag=77c0a68
To: <sip:101@187.107.63.63>
Call-Id: 22a68057-3d80-4e4f-aa5d-9eb0ae4a1120-0000231c@192.168.1.2
CSeq: 8135782 REGISTER
Proxy-Authorization: Digest algorithm=md5,nonce="12821481978:8d8b60e9217f51bf5ff10ddc71c 78efc",realm="3CXPhoneSystem",response="eaa36c4d044a1600ad62 a7dcfaddcc98",uri="sip:187.107.63.63",username="101"
Expires: 3600
Max-Forwards: 70
Contact: <sip:101@192.168.1.2:5090>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-101: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#2, 562 Ms, From: 187.107.63.63:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5090;rport=5090;branch=z9hG4bK077c502e;received= 75.73.79.80
Contact: <sip:101@192.168.1.2:5090>;expires=3600
To: <sip:101@187.107.63.63>;tag=bf7dda0b
From: <sip:101@187.107.63.63>;tag=77c0a68
Call-ID: 22a68057-3d80-4e4f-aa5d-9eb0ae4a1120-0000231c@192.168.1.2
CSeq: 8135782 REGISTER
User-Agent: 3CXPhoneSystem
Content-Length: 0

************* Log Closed (Apr 19 13:49:23) *************



So everything now looks OK.


We will also briefly test basic call operations next using your server. We will repost that later.


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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: April 19 2007 at 2:37pm | IP Logged Quote Jalal
Hi

Thanks for your detailed report. Feel free to test any needed issue with our server. It is just a test server.

Is there any other SIP authentication message like 407 that would be received from Proxy or Registerar that is not supported yet? I asked this question because we have the same problem with Mitel IP PBX. If you want I can prepare you a log for Mitel IP PBX authentication as soon as possible.

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 19 2007 at 3:08pm | IP Logged Quote support
Jalal,


You >>>
Is there any other SIP authentication message like 407 that would be received from Proxy or Registerar that is not supported yet?

<<< Support
I don’t think so. Authentication challenges are either 401 or 407 responses. The media handles them as per the latest sip rfc.

You >>>
If you want I can prepare you a log for Mitel IP PBX authentication as soon as possible.

<<< Support
That would be good. Go ahead and post it to this thread.


Other info:
As per the latest SIP RFC, all non REGISTER authentication challenges should be using 407 challenge responses. REGISTER operations are handled differently (using 401 challenge responses). Why the SIP RFC had to define 2 types of authentication challenge responses seems stupid. It just adds confusion and extra work as far as we are concerned.

We would expect that all other SIP messages (not including REGISTER) to be challenged by the 3CX pbx and the Mitel VOIP switch using 407 responses. If this is the case, then there is no more work to do. If either one of them uses 401 challenge responses for SIP messages that are not REGISTERs, then we have a problem. In this case the 3CX and Mitel guys need to read the SIP RFC.

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: April 19 2007 at 4:01pm | IP Logged Quote support
Jalal,

We ended up configuring our own 3CX PBX here in the lab. For some reason access to your server is very slow.

We performed additional basic inter-op testing by initiating calls, performing call hold and un-hold operations and call terminations.

Things basically look OK.

Here is an example SIP log from one of our media engine apps we use here for testing:

Code:

************* Log Opened (Apr 19 15:55:33) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#92, 2765 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07efc614
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd78c;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>
Contact: <sip:100@192.168.1.2:5080>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15695923 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 222
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#81, 2875 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc614
Proxy-Authenticate: Digest nonce="12821489733:b5141abf4081eab7df0f71294074efc2",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:101@192.168.1.140>;tag=e16aa376
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd78c;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15695923 INVITE
User-Agent: 3CXPhoneSystem
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#93, 110 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc614
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd78c;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=e16aa376
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15695923 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#94, 0 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07efc682
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>
Contact: <sip:100@192.168.1.2:5080>;x-inst="VGVzdCBDYWxsIERhdGE gZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696033 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="12821489733:b5141abf4081eab7df0f7129407 4efc2",realm="3CXPhoneSystem",response="9eb551aea737d69c721f 2610f0c0f5af",uri="sip:101@192.168.1.140",username="100"
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 222
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#82, 109 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc682
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696033 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#83, 141 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc682
Contact: <sip:101@192.168.1.140>
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696033 INVITE
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#84, 1515 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc682
Contact: <sip:101@192.168.1.140>
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696033 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
Content-Length: 184

v=0
o=3cxPS 12821489733390 12821489733392 IN IP4 192.168.1.140
s=3cxPS Audio call
c=IN IP4 192.168.1.2
t=0 0
m=audio 8438 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#95, 1781 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efc682
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696033 ACK
Max-Forwards: 70
Route: <sip:101@192.168.1.140>
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#85, 2672 Ms, From: 192.168.1.140:5060) <<<<
INVITE sip:100@192.168.1.2:5080 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bK-d87543-6416da27ed67a728-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:101@192.168.1.140>
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
From: <sip:101@192.168.1.140>;tag=820fee42
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
Content-Length: 258

v=0
o=3cxPS 12821489733390 12821489733393 IN IP4 192.168.1.140
s=3cxPS Audio call
c=IN IP4 192.168.1.140
t=0 0
m=audio 7048 RTP/AVP 0 8 3 98
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:98 telephone-event/8000
a=sendonly


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#96, 2656 Ms, To: 192.168.1.140:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.140:5060;rport;received=192.168.1.140;branch=z9hG4 bK-d87543-6416da27ed67a728-1--d87543-
From: <sip:101@192.168.1.140>;tag=820fee42
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 2 INVITE
Contact: <sip:100@192.168.1.2:5080>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Content-Length: 222
Content-Type: application/sdp

v=0
o=100 133133328 133133328 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8878 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-15


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#86, 110 Ms, From: 192.168.1.140:5060) <<<<
ACK sip:100@192.168.1.2:5080 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bK-d87543-fe06db5820264112-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:101@192.168.1.140>
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
From: <sip:101@192.168.1.140>;tag=820fee42
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 2 ACK
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#87, 1343 Ms, From: 192.168.1.140:5060) <<<<
INVITE sip:100@192.168.1.2:5080 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bK-d87543-e8603d09f669d56b-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:101@192.168.1.140>
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
From: <sip:101@192.168.1.140>;tag=820fee42
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 3 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
Content-Length: 184

v=0
o=3cxPS 12821489733390 12821489733394 IN IP4 192.168.1.140
s=3cxPS Audio call
c=IN IP4 192.168.1.2
t=0 0
m=audio 8438 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#97, 1453 Ms, To: 192.168.1.140:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.140:5060;rport;received=192.168.1.140;branch=z9hG4 bK-d87543-e8603d09f669d56b-1--d87543-
From: <sip:101@192.168.1.140>;tag=820fee42
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 3 INVITE
Contact: <sip:100@192.168.1.2:5080>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Content-Length: 222
Content-Type: application/sdp

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


<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#88, 110 Ms, From: 192.168.1.140:5060) <<<<
ACK sip:100@192.168.1.2:5080 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bK-d87543-d35eca545b2d9832-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:101@192.168.1.140>
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
From: <sip:101@192.168.1.140>;tag=820fee42
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 3 ACK
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#98, 1235 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07efff2d
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Contact: <sip:100@192.168.1.2:5080>
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696034 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 218
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#89, 1218 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efff2d
Proxy-Authenticate: Digest nonce="12821489740:9e3855f2fa9f9f60be0a0e63769de36d",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696034 INVITE
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#99, 93 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efff2d
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696034 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#100, 63 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07efaf7d
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Contact: <sip:100@192.168.1.2:5080>
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696035 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="12821489740:9e3855f2fa9f9f60be0a0e63769 de36d",realm="3CXPhoneSystem",response="7873ad88eecaf7b7556c 75e0ff501f5e",uri="sip:101@192.168.1.140",username="100"
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 218
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#90, 157 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efaf7d
Contact: <sip:101@192.168.1.140>
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696035 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
Content-Length: 199

v=0
o=3cxPS 12821489733390 12821489733395 IN IP4 192.168.1.140
s=3cxPS Audio call
c=IN IP4 192.168.1.140
t=0 0
m=audio 7048 RTP/AVP 0 98
a=rtpmap:0 PCMU/8000
a=rtpmap:98 telephone-event/8000


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#101, 94 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efaf7d
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696035 ACK
Max-Forwards: 70
Route: <sip:101@192.168.1.140>
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#102, 1062 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07f00841
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Contact: <sip:100@192.168.1.2:5080>
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696036 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 222
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#91, 1156 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07f00841
Proxy-Authenticate: Digest nonce="12821489741:95675f3c2106b0ed3f3cc62999d952eb",algorit hm=MD5,realm="3CXPhoneSystem"
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696036 INVITE
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#103, 94 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07f00841
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696036 ACK
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#104, 16 Ms, To: 192.168.1.140:5060) >>>>
INVITE sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport;branch=z9hG4bK07efebd8
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Contact: <sip:100@192.168.1.2:5080>
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696037 INVITE
Max-Forwards: 70
Organization: 27C1E9D3-D533-4A31-B05B-937D47AE2FB6
Proxy-Authorization: Digest algorithm=md5,nonce="12821489741:95675f3c2106b0ed3f3cc62999d 952eb",realm="3CXPhoneSystem",response="a349b6d961a2aa775112 0d51f6e63fd9",uri="sip:101@192.168.1.140",username="100"
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 222
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#92, 203 Ms, From: 192.168.1.140:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efebd8
Contact: <sip:101@192.168.1.140>
To: <sip:101@192.168.1.140>;tag=820fee42
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696037 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Content-Type: application/sdp
Content-Length: 196

v=0
o=3cxPS 12821489733390 12821489733396 IN IP4 192.168.1.140
s=3cxPS Audio call
c=IN IP4 192.168.1.2
t=0 0
a=recvonly
m=audio 8438 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
a=sendrecv


>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#105, 187 Ms, To: 192.168.1.140:5060) >>>>
ACK sip:101@192.168.1.140 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5080;rport=5080;branch=z9hG4bK07efebd8
From: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
To: <sip:101@192.168.1.140>;tag=820fee42
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 15696037 ACK
Max-Forwards: 70
Route: <sip:101@192.168.1.140>
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
x-CustomHeader-Extension-100: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#93, 1953 Ms, From: 192.168.1.140:5060) <<<<
BYE sip:100@192.168.1.2:5080 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.140:5060;branch=z9hG4bK-d87543-3231a63a9967aa11-1- -d87543-;rport
Max-Forwards: 70
Contact: <sip:101@192.168.1.140>
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
From: <sip:101@192.168.1.140>;tag=820fee42
Call-ID: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 4 BYE
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#106, 1953 Ms, To: 192.168.1.140:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.140:5060;received=192.168.1.140;rport=5060;branch= z9hG4bK-d87543-3231a63a9967aa11-1--d87543-
From: <sip:101@192.168.1.140>;tag=820fee42
To: "Extension 100" <sip:100@192.168.1.140>;tag=7efd7fa;x-UaId=xxxxx-yyyy- zzzzzz
Call-Id: 2d005f01-9538-4447-84f2-357c266dd511-0000266c@192.168.1.2
CSeq: 4 BYE
User-Agent: LanScape VOIP Media Engine/5.12.3.20 (www.LanScapeCorp.com)
Content-Length: 0


************* Log Closed (Apr 19 15:55:48) *************




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


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

Thanks for your new version. Our problem is solved by your 5.12.3.27 version. But unfortunately we should set appropriate Realm for different proxies. I think you can save Realm string when SIP/2.0 407 Proxy Authentication Required is received and send this Realm on your next REGISTER sip message.

I checked sending Realm string by some other softphones and it seems all of them do sending appropriate Realm automatically.

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


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


At the moment the media engine needs to be configured with authentication credentials on a per realm basis. For example:

If your VOIP app wants to be able to authenticate with say 2 different VOIP domains (i.e 2 different authentication realms), then you need to tell the media engine the authentication user name and password for each authentication realm.

That is how the media engine works right now. If you want to support what you are talking about, you can do it but it will take some additional coding effort on your part. Here is how you can achieve the same results:

1)
Monitor all incoming received SIP messages by having your app handle the SipModifySipMessage event. Look at each SIP response line in the message and filter all “401 Unauthorized” and “407 Proxy Authentication Required” Sip messages.

2)
For 401 responses, parse into the SIP response for the “WWW-Authenticate:” Sip header.
It will look something like:

WWW-Authenticate: Digest realm="ps", nonce="9828a7ceba30233d4ec8e6fa6b8c9c2e", opaque="4105de8e65e687436fdab7309608a89a"

Parse the realm value from the header and then call the AddAuthorizationCredentials() API procedure in your SipModifySipMessage event handler code to add a new login name and password for the realm that was specified in the SIP response.

3)
For 407 responses, the steps are identical to the ones above. Parse into the SIP response for the “Proxy-Authenticate:” Sip header.
It will look something like:

Proxy-Authenticate: Digest nonce="12821489733:b5141abf4081eab7df0f71294074efc2,algorith m=MD5,realm="MyNewRealm"

Parse the realm value from the header and then call the AddAuthorizationCredentials() API procedure in your SipModifySipMessage event handler code to add a new login name and password for the realm that was specified in the SIP response.


To make the handling of “generic realms” much easier, and to remove the above coding requirements on the VOIP application, we could allow something like the following to occur:

1)
The media engine is configured with authentication credentials using the AddAuthorizationCredentials() API procedure. In this case the VOIP app could specify “default” authentication user name and password for all unspecified realms like this:

User name: your_multirealm_user_name
Password: your_multirealm_password
Realm: “*”

By specifying the realm to be the “wild card” string, all challenges coming from unspecified realms would use the “common” user name and password to compute the challenge response for whatever real is challenging the media engine.

Let us know what your thoughts are on this. If it’s something that would be useful, then we will put it on the development “to do” list.


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


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

We did know we can change SIP messages manually but we don't want to do this as far as possible.

It seems your suggestion about setting '*' for Realm to be detected and set automatically is good but why '*' and why not '' (empty string). I think '' is more easier for both Media Engine developers and customers using Media Engine's products.

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


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

Because the wildcard "*" string when specified as the realm parameter in the AddAuthorizationCredentials() API procedure is more consistent with the thinking of using a regular expression to signify the dynamic authentication realms.

This is probably just a semantic choice. Ask 10 different people and you will get 10 different answers.

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


Joined: April 24 2006
Location: Iran
Posts: 188
Posted: May 07 2007 at 11:10am | IP Logged Quote Jalal
Ok, no problem about wildcard.

I'm looking forward for your next version adding this feature. I have also added some other issues today. Check it up.

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


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

We had no problem with '*' wildcard added in v5.12.3.28.

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

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

  Post ReplyPost New Topic
Printable version Printable version

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





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