[Asterisk-Users] strange sip behavior (looping back to my own extension vm)
Steven Kokinos
steve at kokinos.com
Wed May 5 09:31:25 MST 2004
Hello-
I am currently testing with a carrier that seems to be having some trouble
around toll-free (800 number) access. While a problem, its the resulting
behavior that I'm finding disconcerting.
When I dial an 800#, I get the following response:
-- Executing Macro("SIP/2700-e10b", "carrier-out|18005558355|70|r") in
new stack
-- Executing SetCallerID("SIP/2700-e10b", "xxxxxx4027") in new stack
-- Executing SetCIDName("SIP/2700-e10b", "Name") in new stack
-- Executing Dial("SIP/2700-e10b", "SIP/18005558355 at carrier|70|r") in
new stack
-- Called 18005558355 at carrier
-- Executing Dial("SIP/-091cb238", "SIP/2700|25|r") in new stack
-- Called 2700
-- Got SIP response 486 "Busy Here" back from xxx.xxx.93.84
-- SIP/2700-552a is busy
== Everyone is busy at this time
-- Executing SetVar("SIP/-091cb238", "CURRENTMAILBOX=2400") in new stack
-- Executing Macro("SIP/-091cb238", "vm|2400|sixthree") in new stack
-- Executing Answer("SIP/-091cb238", "") in new stack
-- Executing BackGround("SIP/-091cb238",
"/var/spool/asterisk/voicemail/sixthree/2400/unavail") in new stack
-- Playing '/var/spool/asterisk/voicemail/sixthree/2400/unavail'
(language 'en')
-- SIP/carrier-95ef is ringing
-- SIP/carrier-95ef answered SIP/2700-e10b
-- Attempting native bridge of SIP/2700-e10b and SIP/carrier-95ef
== Spawn extension (macro-carrier-out, s, 3) exited non-zero on
'SIP/2700-e10b' in macro 'carrier-out'
== Spawn extension (home, 618005558355, 1) exited non-zero on
'SIP/2700-e10b'
== Spawn extension (macro-vm, s, 2) exited non-zero on 'SIP/-091cb238' in
macro 'vm'
== Spawn extension (carrier-in, 6134824027, 3) exited non-zero on
'SIP/-091cb238'
More information about the asterisk-users
mailing list