will see the results you presented. I see you have the peer set as a dynamic
host, and if the IP address of the device does in fact change then registration
is appropriate.
--------------010105020708030401070201
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 11/22/2011 07:29 AM, Jonas Kellens wrote:
<blockquote cite="mid:4ECBBFCF.2020204 at telenet.be"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
On 11/22/2011 04:25 PM, Bruce Ferrell wrote:
<blockquote cite="mid:4ECBBEE1.3020008 at baywinds.org"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
Jonas,<br>
<br>
May I suggest that you present us your sip.conf entry for this
peer, properly redacted, of course. That might help
more. What
I do for "gateways" at known addresses is to put an entry like
this into the sip.conf entry:<br>
<br>
<br>
[peer]<br>
type=peer<br>
defaultip=192.168.40.123<br>
insecure=invite,port<br>
context=some_context<br>
<br>
</blockquote>
<font face="Helvetica, Arial, sans-serif"><br>
</font><font face="Helvetica, Arial,
sans-serif"><br>
This is the peer definition in sip.conf :<br>
<br>
[</font><font face="Helvetica, Arial,
sans-serif">SIPPEERusername]<br>
type=friend<br>
host=dynamic<br>
defaultuser=</font><font face="Helvetica, Arial,
sans-serif">SIPPEERusername<br>
secret=guessthis<br>
context=from-PEERTRUNK<br>
nat=yes<br>
dtmfmode=rfc2833<br>
canreinvite=no<br>
disallow=all<br>
allow=alaw<br>
allow=gsm<br>
<br>
<br>
Hope you can help me out with this extra information.<br>
<br>
</font><br>
Kind regards,<br>
<br>
Jonas.<br>
</blockquote>
From what I see in your entry, you are requiring registration from
the peer. The next thing i would check is to see if the
registration has succeeded. If it doesn't succeed, you will
see the
results you presented. I see you have the peer set as a dynamic
host, and if the IP address of the device does in fact change then
registration is appropriate.<br>
</body>
</html>
--------------010105020708030401070201--