I think this means that it attempted to create a native bridge, which is
that it was trying to have the call go directly between the two
endpoints instead of going through the asterisk server but that process
failed. So in that case, Asterisk continued to proxy the call data. If
that's the case, a better output might have been, "... was
unsuccessful,
server will continue to bridge call," or something along those lines.
MARK.
David Bandel wrote:> Folks,
>
> Just cleared a call and had this on the CLI:
>
> -- Executing Macro("SIP/david-75e3",
"voicemail|sip/craigo") in new stack
> -- Executing Dial("SIP/david-75e3",
"sip/craigo|20|m") in new stack
> -- Called craigo
> -- Started music on hold, class 'default', on channel
'SIP/david-75e3'
> -- SIP/craigo-88db is ringing
> -- SIP/craigo-88db answered SIP/david-75e3
> -- Stopped music on hold on SIP/david-75e3
> -- Attempting native bridge of SIP/david-75e3 and SIP/craigo-88db
> -- Native bridge of SIP/david-75e3 and SIP/craigo-88db was unsuccessful
> == Refreshing DNS lookups.
> == Spawn extension (macro-voicemail, s, 1) exited non-zero on
> 'SIP/david-75e3' in macro 'voicemail'
> == Spawn extension (longdistance, 1001, 1) exited non-zero on
'SIP/david-75e3'
>
> Odd thing is this call was successful. We talked for about 10
> minutes. So why would the SIP-SIP native bridge say UNsuccessful?
>
> David A. Bandel
> --
> Focus on the dream, not the competition.
> - Nemesis Air Racing Team motto
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>