Outbound Phone Calls with 3rd Party SIP VoIP providers

[Moonshine]

I've been using Windows Messenger (Voice & Video) with the .NET service since
the introduction of XP.

I'm now starting to experiment with SIP based VoIP using a 3rd Party service
provider (VoIPTalk.org)

The account allows for both inbound and outbound PSTN calls.

I really want to be able to carry on using "Messenger" as my Communications
client of choice.

I've yet to determine 100% if it is possible to make outbound "Phone Calls" with
messenger (either MSN or Windows variety) without being subscribed to one of the
MS "Prefered" VoIP service providers.

In bound calls are fine, and I've been able to test outbound using the Xten
SoftPhone so I know the service is working. But I don't want to have to use a
separate Client just for the SIP VoiP service if at all possible.

Thanks

 

[Moonshine]

I've been using Windows Messenger (Voice & Video) with the .NET service since
the introduction of XP.

I'm now starting to experiment with SIP based VoIP using a 3rd Party service
provider (VoIPTalk.org)

The account allows for both inbound and outbound PSTN calls.

I really want to be able to carry on using "Messenger" as my Communications
client of choice.

I've yet to determine 100% if it is possible to make outbound "Phone Calls" with
messenger (either MSN or Windows variety) without being subscribed to one of the
MS "Prefered" VoIP service providers.

In bound calls are fine, and I've been able to test outbound using the Xten
SoftPhone so I know the service is working. But I don't want to have to use a
separate Client just for the SIP VoiP service if at all possible.

Thanks

No one going to answer me on this one :-( ?

 

[Fred]

To make outbound phone calls with messenger you must sign up with a
Messenger only account with one of the few companies that still offer one.
I am not aware of any company that offered a Sip based messenger account. so
I do not think it is possible to do what you would like. Years ago I closed
my messnger only phone account and go a SIP based account from one of the
many companies that offer one.
Fred

 

[Moonshine]

To make outbound phone calls with messenger you must sign up with a
Messenger only account with one of the few companies that still offer one.
I am not aware of any company that offered a Sip based messenger account. so
I do not think it is possible to do what you would like. Years ago I closed
my messnger only phone account and go a SIP based account from one of the
many companies that offer one.
Fred

OK thanks for the confirmation, that's a bummer.

If there is a way to modify the registry or something to enable 3rd Party SIP
connection I'd luv to know

 

[Moonshine]

OK thanks for the confirmation, that's a bummer.

If there is a way to modify the registry or something to enable 3rd Party SIP
connection I'd luv to know

OK I'm getting up to speed with SIP VoIP pretty quick and have now established
that the problem with Windows Messenger, and the reason it won't work with 3rd
party VoIP telephone provides for PSTN break out calls is that it does not
support the "Proxy Authentication" feature in the SIP protocol.

A PSTN breakout type call is placed in exactly the same way as a SIP user to SIP
user call, the difference being that for the SIP user to SIP user call the 3rd
Party VoIP provider does not ask for Proxy Authentication. So the call from
Messenger to IP Phone on same providers network works. For the PSTN break out
call because there are costs involved, the VoIP provider asks for "Proxy
Authentication" during the call set-up. Windows Messenger does not appear to
support this and the call fails

Here is a sample of the SIP call set-up showing the response to the INVITE
requesting Proxy Authentication...


Session Initiation Protocol
Status-Line: SIP/2.0 407 Proxy Authentication Required
Status-Code: 407
Message Header
Via: SIP/2.0/UDP 123.123.123.123:5655
From: "(e-mail address removed)"
<sip:[email protected]>;tag=9512aa538be144ae9bfc20391f1f7a79;epid=1df98d4510
SIP from address: "(e-mail address removed)" <sip:[email protected]>
SIP tag: 9512aa538be144ae9bfc20391f1f7a79;epid=1df98d4510
To: <sip:[email protected]>;tag=as73ceecda
SIP to address: <sip:[email protected]>
SIP tag: as73ceecda
Call-ID: [email protected]
CSeq: 1 INVITE
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:[email protected]>
Proxy-Authenticate: Digest realm="asterisk", nonce="68979f1a"
Content-Length: 0


I've changed the actual IP addresses and phone number used.

Comparing the original INVITE with that produced by a real IP Phone the
addressing etc is identical it is just that Windows messenger does not go on to
provide the fresh INVITE with Proxy Authentication when requested.