VoIP Unlock Key Credentials (PBX)

[Jos]

Does some one have the configuration that should be use with the new VoIP Unlock Key Credentials?

Me I am using the following configuration whit my PBX

username=1nxxnxxxxxx
type=peer
secret=mysecret
qualify=yes
nat=no
insecure=invite
host=voip.freephoneline.ca
dtmfmode=inband
disallow=all
context=from-trunk
allow=ulaw

Is their any thing to be change or add?

[Jake]

if you are using a flavour of Asterisk, which it looks like, make sure you have changed the useragent in the sip.conf

Fongo/FPL blocks connections with this useragent (don't ask me why). Otherwise the settings looks fine, there is always a bit of flexibility with certain settings. What problems are you getting?

[Jos]

Thanks Jake for your reply.
I do not have any problem with my PBX it is just that Fongo send user info in a Email:
Dear Customer,
Because you purchased a VoIP Unlock Key from Dell Voice or Freephoneline, we're writing to let you know that the configuration settings for your VoIP Unlock Key are now available online for easy reference. We recommend you review the required settings and best practices for your third party SIP clients (such as ATAs, softphones, or PBXes). View the configuration settings now.


For the Fongo/FPL blocks connections with this useragent this is fix long ago the PBX is running for 2 years now

[Jake]

Ah OK Jos, well then the only other things I changed was the registration time and timeout time. The standard registration time for * is 120 (less than what FPL wants).

This is the two lines I added to my conf files

Code: Select all

defaultexpiry=3600
registertimeout=120

Although I know for one person 3600 messed up another of his trunks. In the SIP settings online it says a value from 180 to 3600; he changed his to 180 and has not had a problem with it as far as I know.

Now I believe the server can send back a 422 response which will change the values for us on *, but it doesn't look like FPL does this. It could save a lot of problems if they did.