SIP not able to recieve/originate calls

[Guest Chiru]

SIP Configured but not able to originate calls and receive calls.

kindly check the log and revert back

 

log.zip

[SupportTeam]

ktTel trace shows:
 

161 102229.972 37380     fn    VoIPProvider_AuthenticationAdd(auth_realm=ktk.voip.ims.bsnl.in, auth_identity=+918277995589, auth_username=+918277995589, auth_password=******)
...
164 102229.979 37380           auth realm:[ktk.voip.ims.bsnl.in] identity:[+918277995589] username:[+918277995589]
...
166 102229.982 37380     fn    VoIPProvider_Register(protocol=SIP, reg_server=ktk.voip.ims.bsnl.in, reg_client=+918277995589@ktk.voip.ims.bsnl.in, local_alias=+918277995589@ktk.voip.ims.bsnl.in, sH323SupportedPrefixes=)
...
205 102334.371 36932     WARN  IPEC_REG_FAIL_internalError : internal IP CCLib error encountered while attempting to formulate an outgoing REGISTER request.
206 102334.371 36932     WARN  **********************************************
207 102334.371 36932     WARN  SIP REGISTER Failed
208 102334.371 36932     WARN  **********************************************

 

Suggest removing the "+" from 'username' and 'identity' fields and restarting the VoiceGuide service to have new settings read in and registered.

You may want to double check with the service provider ( ktk.voip.ims.bsnl.in )  as to what settings need to be used during registration.

WireShark may be useful here to confirm the SIP traffic between VoiceGuide/DialogicHMP and SIP provider.

[SupportTeam]

Once the SIP account registration completes successfully we recommend as the first step to call into the system - by dialing the telephone number linked to the account that VoiceGuide is registering.

Once you confirm inbound calls as working, (ie: you can call into the system and can hear VoiceGuide answer the call) you can then start placing outgoing calls.

For outgoing SIP calls the IP address must be included as part of the number.

eg:

08192255555@ktk.voip.ims.bsnl.in

or if all outgoing calls will be going through the same VoIP provider then you can edit the VG.INI, section [VGDialer] entry: DialedNumberSuffix

eg:

DialedNumberSuffix=@ktk.voip.ims.bsnl.in

The "DialedNumberSuffix" will be added to all the outgoing calls loaded from the outbound calls database.

[Guest Chiru]

as per the service vendor suggestion "+" from 'username' and 'identity' fields should't be removed. is there any other way to get registered with sip?

[SupportTeam]

We tried to use above settings on our test system, and the REGISTER request packets were sent out to ktk.voip.ims.bsnl.in (IP: 218.248.233.142), but no responses were received at all.

We can ping ktk.voip.ims.bsnl.in / 218.248.233.142 from our test system.

Over a course of a minute 14 REGISTER requests were sent out, and eventually after no response we saw the same error in traces that was recorded in your log file.

Next step would be for you confirm whether you are seeing any responses to REGISTER requests on your system. Please use WireShark (www.wireshark.org) to monitor the traffic and see if you get any responses. Please post WireShark trace.

Specify "sip" in WireSharks filter text box to only show SIP traffic (see attached screenshot).

Then use File -> Export Specified Packets to save .pcapng file of just the displayed packets.

The resulting error message seems to be a bit misleading and we will look into that, but the underlying problem seems to be that the SIP service provider is not responding to SIP REGISTER requests - so we need to confirm that this is the problem on your system and if yes then this issue needs to be resolved with your SIP service provider.

 

161 134635.307  2212     fn    VoIPProvider_AuthenticationAdd(auth_realm=ktk.voip.ims.bsnl.in, auth_identity=+918277995589, auth_username=+918277995589, auth_password=******)
...

166 134635.318  2212     fn    VoIPProvider_Register(protocol=SIP, reg_server=ktk.voip.ims.bsnl.in, reg_client=+918277995589@ktk.voip.ims.bsnl.in, local_alias=+918277995589@ktk.voip.ims.bsnl.in, sH323SupportedPrefixes=)
...
205 134740.143   660     WARN  IPEC_REG_FAIL_internalError : internal IP CCLib error encountered while attempting to formulate an outgoing REGISTER request.
206 134740.143   660     WARN  **********************************************
207 134740.143   660     WARN  SIP REGISTER Failed
208 134740.143   660     WARN  **********************************************

 

register_attempt.pcapng

[SupportTeam]

Also, if loading calls using the "Outbound Call Loader" app then you should specify this in the "SIP Gateway" text box:

ktk.voip.ims.bsnl.in

This way the "@ktk.voip.ims.bsnl.in" will be added to each number loaded into the outgoing calls database, and the entry "DialedNumberSuffix" in VG.INI section [VGDialer] can be left blank.