I'll hazard a guess. When a Sipura device does a "forward" it sends a SIP "temporarily moved" message back to the originator, with the URI that you are forwarding to. If this is another SIP device, this is pretty easy, as Asterisk just re-invites. The problem is when it tries to re-invite to itself, it gets a little confused. At least that's what I took from the documentation. Based on your debug output, it looks like it is trying to re-invite to a context called main. Does this context exist, and are the appropriate extensions in it?
-Tim On July 20, 2006 11:25, Vahan Yerkanian wrote: > Greetings folks, > > Could I ask a minute of your attention on the bug I've posted at > http://bugs.digium.com/view.php?id=7557 ? > > I'm clueless what is the cause of it. > > In short, if you set on any Sipura device (tested with 2100/3000/941) a > "Cfwd all" (*72 service by default) to a queue or moh extension number, > asterisk core dumps every time you call that device extension. If you > put a direct extension (e.g. another sip device extension), call gets > through. > > Anyone able to reproduce this? > > Thanks for your time, > Vahan > _______________________________________________ > Asterisk-BSD mailing list > [email protected] > http://lists.digium.com/mailman/listinfo/asterisk-bsd -- Tim St. Pierre IP telephony specialist sip://[EMAIL PROTECTED] Toronto: 647 722 6930 Toll-Free 1 888 488 6940 [EMAIL PROTECTED]
pgpOYvVQMgcP3.pgp
Description: PGP signature
_______________________________________________ Asterisk-BSD mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-bsd
