Register SIP

[Frank.Schwarz]

I'm trying to do a VG test install. A SIP line is to be registered. HMP is installed. The computer is new. Firewall is disabled. UAC is disabled. With a tool MicroSip Portable I can connect to the line and make calls. Attached is a PDF with the ConfigFile and the Wireshark logs. Can you please help me?

Regards Frank

1_Try_VG.pcapng

2_Try_VG.pcapng

3_Try_VG.pcapng

4_Try_VG.pcapng

MicroSIP_portable.pcapng

Registerversuche.pdf

[SupportTeam]

The "3_Try" and "4_Try" attempts show your SIP PB (AASTRA OpenCom 150 ?) respond with a "401 Unauthorized".

So looks like the Authentication on VoiceGuide side was not correctly set up as VoiceGuide was not responding to the 401 with an authenticated Register.

 

In your <VoIP_Authentication> section in the Config.xml file what is the value in the <AuthUsername> field?

Have you tried using:

40

or:

40@10.92.50.252

 

Also, the <RegClient> in the <VoIP_Registration> section should be:

40@10.92.50.252

 

Please post VoiceGuide's vgEngine and ktTel traces capturing VoiceGuide service startup if you still encounter issues.

 

 

 

 

 

 

 

 

 

 

[Frank.Schwarz]

Sorry, I've been testing a wide variety of settings for a few hours. I renamed the user name in the telephone system from UserSIP to 40... no success With MicroSIP I type in the required values and immediately i have a connect.

 

When I use these settings I get Forbidden... What can I do???

<VoIP_Registrations>

<VoIP_Registration>
<Display></Display>
<Protocol></Protocol>
<RegServer>10.92.50.252</RegServer>
<RegClient>40@10.92.50.252</RegClient>
<LocalAlias></LocalAlias>
<Expires></Expires>
</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>
<Display>SIP</Display>
<Realm></Realm>
<Identity></Identity>
<AuthUsername>40</AuthUsername>
<AuthPassword>[password_removed]</AuthPassword>
</VoIP_Authentication>

</VoIP_Authentications>

Forbidden.pcapng

[SupportTeam]

Trace shows the SIP Authentication is now correctly set up from VoiceGuide's side.

The "401 Unauthorized" is correctly replied to by VoiceGuide with the second REGISTER containing the response code.

You will need to ask the administrator of the PBX at 10.92.50.252 as to why that PBX replied with 403 Forbidden to this valid SIP REGISTER.

Is it possible that this PBX is only allowing extensions to be registered using certain types of soft-phone only, and not all generic SIP devices?

The logs from PBX at 10.92.50.252 should show why that PBX decided to reject what looks to be a valid standard-SIP registration.