Author |
|
speedvoip Vetran
Joined: August 07 2008 Location: Canada Posts: 156
|
Posted: October 18 2008 at 2:05pm | IP Logged
|
|
|
Hi Support:
Sorry for my continuous posting about registration failure. As u know, if the media engine receives a challenge to a REGISTER request sent to registrar, it should be responding with a new REGISTER with computed authentication credentials.
I have been trying register my own sip account with public deltathree sip server with console based sample DialerTest. But always failure. I am sure that my own authentication credentials for registration is correct and I have modified source code of DialerTest to have my credentials built into it. However after many times of efforts, DialerTest complains as follows:
"Error: Could not enable registrar support. Error code: SipRegisterAuthorizationError".
I have checked reference manual for error info which reminds me AddAuthorizationCredentials() API should be performed prior to EnableSipRegisterServer() is called. In fact DialerTest source code does that per above instruction.
On the other hands, in terms of SIP exchange, when 401 response is received, media engine do not transmit second new register request with computed authentication credentials.
Here is Log:
Code:
************* Log Opened (Oct 19 02:23:13) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [02:23:14.322] 0 Ms, To: 213.137.73.140:5060) >>>>
REGISTER sip:deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.3:5061;rport;branch=z9hG4bK00d74e20
From: <sip:23813073@deltathree.com>;tag=d733c5
To: <sip:23813073@deltathree.com>
Call-Id: 751bdad4-3ae2-4009-8e5b-94ccdcd1fd8b-000011e0@192.168.1.3
CSeq: 14099340 REGISTER
Expires: 36000
Max-Forwards: 70
Contact: <sip:23813073@192.168.1.3:5061>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.14 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [02:23:14.587] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.3:5061;rport;branch=z9hG4bK00d74e20
To: <sip:23813073@deltathree.com>
From: <sip:23813073@deltathree.com>;tag=d733c5
Call-ID: 751bdad4-3ae2-4009-8e5b-94ccdcd1fd8b-000011e0@192.168.1.3
CSeq: 14099340 REGISTER
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [02:23:14.588] 1 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.3:5061;rport;branch=z9hG4bK00d74e20
To: <sip:23813073@deltathree.com>
From: <sip:23813073@deltathree.com>;tag=d733c5
Call-ID: 751bdad4-3ae2-4009-8e5b-94ccdcd1fd8b-000011e0@192.168.1.3
CSeq: 14099340 REGISTER
WWW-Authenticate: DIGEST realm="deltathree.com", nonce="daa485026661c7a605a1031be6402ed6", algorithm=MD5
Content-Length: 0
************* Log Closed (Oct 19 02:23:14) *************
|
|
|
So I am puzzeled. What is on earth something wrong ?
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: October 18 2008 at 2:15pm | IP Logged
|
|
|
Hi George,
Normally we don’t handle support issues on Saturday but we were performing other dev work and are just about to complete a solution for you.
Hang on… we have fixed the issue and will repost shortly.
Thanks bud,
Support
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: October 18 2008 at 2:42pm | IP Logged
|
|
|
Hi George,
You are going to cry when we tell you what the problem was.
When the media engine received the challenge response from your provider, the authentication type specified in the 401 response was all capitol letters “DIGEST”.
When the media engine parsed the SIP 401 response, it had a parse error because the authentication type was not “Digest”. Notice the case difference.
Anyway, we updated the WWW and proxy authentication parsing code in the media engine to handle any authentication type whatever the case. We performed a few tests and all looks OK. We even tried to call our self via the service provider but I guess they don’t route calls back to the same SIP user agent. We are glad you identified this for us. We hope you have not wasted a ton of time on this. Just a simple snafu…
Here is a SIP log using the latest v6 media engine:
Code:
************* Log Opened (Oct 18 14:29:31) *************
>>>> TxTxTxTxTx (#1, [14:29:46.843] 0 Ms, To: 213.137.73.140:5060) >>>>
REGISTER sip:natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d33a69
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
To: <sip:40452728@natrelay.deltathree.com>
Call-Id: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837452 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:40452728@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#1, [14:29:46.906] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d33a69
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837452 REGISTER
Content-Length: 0
<<<< RxRxRxRxRx (#2, [14:29:46.906] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d33a69
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837452 REGISTER
WWW-Authenticate: DIGEST realm="deltathree.com", nonce="3b39291f46e42700b51b73de65ad9243", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTx (#2, [14:29:46.906] 63 Ms, To: 213.137.73.140:5060) >>>>
REGISTER sip:natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d32b4b
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
To: <sip:40452728@natrelay.deltathree.com>
Call-Id: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837453 REGISTER
Authorization: Digest algorithm=md5,nonce="3b39291f46e42700b51b73de65ad9243",
realm="deltathree.com",response="856fc798aa80093c0e376c06bc0cc791",
uri="sip:natrelay.deltathree.com",username="40452728"
Expires: 3600
Max-Forwards: 70
Contact: <sip:40452728@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#3, [14:29:46.968] 62 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d32b4b
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837453 REGISTER
Content-Length: 0
<<<< RxRxRxRxRx (#4, [14:29:46.968] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d32b4b
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33874
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837453 REGISTER
Contact: <sip:40452728@213.137.73.104:5060;user=phone;transport=udp>;action=proxy;expires=900
Expires: 900
Content-Length: 0
>>>> TxTxTxTxTx (#3, [14:29:50.343] 3437 Ms, To: 213.137.73.140:5060) >>>>
INVITE sip:40452728@natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34f51
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d39870;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>
Contact: <sip:40452728@192.168.1.2:5088>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867212 INVITE
Max-Forwards: 70
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 439
User-Agent: LanScape Utility Softphone/5.10.0.4
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
v=0
o=40452728 114498296 114498296 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 12002 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16
<<<< RxRxRxRxRx (#5, [14:29:50.406] 3438 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34f51
To: <sip:40452728@natrelay.deltathree.com>
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d39870;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867212 INVITE
Content-Length: 0
<<<< RxRxRxRxRx (#6, [14:29:50.406] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34f51
To: <sip:40452728@natrelay.deltathree.com>
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d39870;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867212 INVITE
Proxy-Authenticate: DIGEST realm="deltathree.com", nonce="d985991b91705b7371c4b0e3246dc37d", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTx (#4, [14:29:50.406] 63 Ms, To: 213.137.73.140:5060) >>>>
ACK sip:40452728@natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34f51
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d39870;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>
Call-Id: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867212 ACK
Max-Forwards: 70
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
>>>> TxTxTxTxTx (#5, [14:29:50.406] 0 Ms, To: 213.137.73.140:5060) >>>>
INVITE sip:40452728@natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34fa1
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d398c0;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>
Contact: <sip:40452728@192.168.1.2:5088>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867276 INVITE
Max-Forwards: 70
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Proxy-Authorization: Digest algorithm=md5,nonce="d985991b91705b7371c4b0e3246dc37d",
realm="deltathree.com",response="47c86da7f2a5ab1ddeeca90482c983ec",
uri="sip:40452728@natrelay.deltathree.com",username="40452728"
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 439
User-Agent: LanScape Utility Softphone/5.10.0.4
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
v=0
o=40452728 114498375 114498375 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 12002 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16
<<<< RxRxRxRxRx (#7, [14:29:50.484] 78 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34fa1
To: <sip:40452728@natrelay.deltathree.com>
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d398c0;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867276 INVITE
Content-Length: 0
<<<< RxRxRxRxRx (#8, [14:29:50.515] 31 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34fa1
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d398c0;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>;tag=fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248
Call-ID: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867276 INVITE
Content-Length: 0
<<<< RxRxRxRxRx (#9, [14:29:53.671] 3156 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34fa1
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d398c0;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>;tag=fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248
Call-ID: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867276 INVITE
Content-Length: 0
>>>> TxTxTxTxTx (#6, [14:29:53.750] 3344 Ms, To: 213.137.73.140:5060) >>>>
ACK sip:40452728@natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34fa1
From: "LanScape Phone 40452728" <sip:40452728@natrelay.deltathree.com>;tag=6d398c0;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:40452728@natrelay.deltathree.com>;tag=fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248
Call-Id: fca6fcc0-2cad-4abe-8aae-379fe29bea92-00007248@192.168.1.2
CSeq: 13867276 ACK
Max-Forwards: 70
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
>>>> TxTxTxTxTx (#7, [14:29:56.250] 2500 Ms, To: 213.137.73.140:5060) >>>>
REGISTER sip:natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d37a42
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
To: <sip:40452728@natrelay.deltathree.com>
Call-Id: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837454 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:40452728@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#10, [14:29:56.312] 2641 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d37a42
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837454 REGISTER
Content-Length: 0
<<<< RxRxRxRxRx (#11, [14:29:56.312] 0 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d37a42
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837454 REGISTER
WWW-Authenticate: DIGEST realm="deltathree.com", nonce="9416e444fc412d349f0795d6fef746ae", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTx (#8, [14:29:56.312] 62 Ms, To: 213.137.73.140:5060) >>>>
REGISTER sip:natrelay.deltathree.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34b1d
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
To: <sip:40452728@natrelay.deltathree.com>
Call-Id: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837455 REGISTER
Authorization: Digest algorithm=md5,nonce="9416e444fc412d349f0795d6fef746ae",
realm="deltathree.com",response="5f67aa800c345a0915dcf6b99fac5726",
uri="sip:natrelay.deltathree.com",username="40452728"
Expires: 0
Max-Forwards: 70
Contact: <sip:40452728@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-40452728: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#12, [14:29:56.359] 47 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34b1d
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837455 REGISTER
Content-Length: 0
<<<< RxRxRxRxRx (#13, [14:29:56.375] 16 Ms, From: 213.137.73.140:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06d34b1d
To: <sip:40452728@natrelay.deltathree.com>
From: <sip:40452728@natrelay.deltathree.com>;tag=6d33247
Call-ID: ba20485f-82e6-43f4-87b9-94608cb22939-00007248@192.168.1.2
CSeq: 13837455 REGISTER
Contact: <sip:40452728@213.137.73.104:5060;user=phone;transport=udp>;action=proxy;expires=900
Expires: 900
Content-Length: 0
************* Log Closed (Oct 18 14:29:58) *************
|
|
|
We will send you via email a v6 “engineering release” so you can get on with your work. Also note that we added a new API proc called SetUserAgentInfo() that will allow you to set the “User-Agent:” SIP header for all transmitted SIP messages. Hust call this new API proc once after the engine is running and the media engine will handle the rest.
Don’t worry about posting to this forum. As long as its constructive stuff, its all good. :)
Thanks,
Support
|
Back to Top |
|
|
speedvoip Vetran
Joined: August 07 2008 Location: Canada Posts: 156
|
Posted: October 19 2008 at 10:12pm | IP Logged
|
|
|
Hi Support:
If u don't mind, would u send source code of Lanscape Utility Softphone used for your internal testing to me for reference? Currently, I am involving in development of project dialer.
Thanks!
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: October 20 2008 at 12:39pm | IP Logged
|
|
|
Hi George,
Unfortunately we can’t let that source code out. Frankly the C/C++ source code is only used by us developers and is not pretty. Not that the test utility soft phone code is bad – mind you, its just that we use the test app for many test scenarios and we would not want to give customers the impression that the code for the utility soft phone is a typical example of our work. You know what I mean?
Anyway, don’t worry about having that source code. Once you get started on your call dialer app, we support you for up to two months during your development. After that, we suggest customers work with us using a simple support agreement structure.
We will be able to help you and give you more concise info and examples – better that looking at the source code for the utility soft phone.
By the way, not that managed code is bad, but we hope you are going to develop your VOIP app using C/C++ if possible if you are thinking about a high line density deployment.
Support
|
Back to Top |
|
|
|
|