Busy Signal
 

I have set up an account with LINK2VOIP and added this account to VOXALOT. I can make calls using this provider without problem but if I call my LINK2VOIP account thru its DID, I get a busy signal. My account is shown as Registered. I contacted LINK2VOIP technical support but they asked me to provide a trace.

If I setup my new LINK2VOIP account under X-LITE, the softphone rings OK.

Any suggestion?

A trace would help, however what happens when you disconnect your client from Voxalot? Does the call goto Voxalot voicemail?
.

No...busy signal

Please PM me your Voxalot account.
.

I just sent you a private message

Ok, your problem is that the provider is sending the INVITE to the wrong user.

Allow me to explain:

When Voxalot registers with a provider (or when any SIP client registers with a provider for that matter) the REGISTER sends a contact. For Voxalot, the contact will be:

sip:xxxxxx@voxalot-proxy where xxxxxx is *your* Voxalot account.

When an inbound call comes from that provider, the SIP INVITE should be sent to the contact. ie sip:xxxxxx@voxalot-proxy

In your case, the provider is sending it to:

sip:M*T8**1@voxalot-proxy where M*T8**1 is a masked version of your LINK2VOIP username.

Now, when Voxalot receives this message it has no clue who M*T8**1 is as it is expecting the provider to honor the contact that was sent on REGISTER as per the SIP RFC.

Another provider in Australia (MNF) had a similar issue a little while back and subsequently fixed it on their end. Unfortunately to resolve this problem, the provider must honor the CONTACT passed to them in the SIP REGISTER and all subsequent calls *must* use this CONTACT.

We have a good relationship with the folks at LINK2VOIP and we are more than happy to discuss this matter with them if you send them our way. I have PMed you a snippet of the SIP trace that you can send to them.

Thanks.

Thank you so much. Your help is much appreciated.

I forwarded the INFO to the LINK2VOIP support team.

Gilles

This is the response that I got from LINK2VOIP...any comment?:

Andrew Green stated the following:

[andrew - Fri Jul 13 17:27:18 2007]:
> This is a major misunderstanding on his part (I think :) )...
>
> When we send a DID call to your server we send it to DID#@registered
> host via the registered and authenticated user. If you needed incoming
> calls to be from/to a user of 455447 then you should have created the
> Link2VoIP username as '455447' not 'AAA9999' which is your current
> username.
>

This is the way LINK2VOIP have chosen to implement their DIDs. That said, my comment still stands that SIP INVITEs should be sent to CONTACT passed in the registration:

See http://www.ietf.org/rfc/rfc3261.txt

10.2.1 Adding Bindings

The contact address sent by Voxalot contains the Voxalot username not the Link2VoIP username. Subsequent INVITES should be sent to the contact address Voxalot sends.

Martin,

Where you say voxalot-proxy, do you mean to say voxalot.com ?

It is my understanding that you previously said that a voxalot SIP URI should use voxalot.com regardless of the preferred server used in the registration process.

AndrewM