On 11/22/2011 07:29 AM, Jonas Kellens wrote: > On 11/22/2011 04:25 PM, Bruce Ferrell wrote: >> >> Jonas, >> >> 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: >> >> >> [peer] >> type=peer >> defaultip=192.168.40.123 >> insecure=invite,port >> context=some_context >> > > > This is the peer definition in sip.conf : > > [SIPPEERusername] > type=friend > host=dynamic > defaultuser=SIPPEERusername > secret=guessthis > context=from-PEERTRUNK > nat=yes > dtmfmode=rfc2833 > canreinvite=no > disallow=all > allow=alaw > allow=gsm > > > Hope you can help me out with this extra information. > > > Kind regards, > > Jonas. >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.
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello
asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
