Displaying 5 results from an estimated 5 matches for "mydids".
Did you mean:
mydid
2009 Sep 15
0
1.6.2.0-rc1 intermittent voicemail problem ?
1.6.2.0-rc1. I am having trouble with voice mail intermittently not
working correctly on CHANUNAVAIL. (it may happen for other statuses
too, haven't checked). Basically here's what happens:
-- Executing [1651xxxxxx at mydids:1]
Macro("SIP/ipkall-trunk-14838bc8", "phone,1651xxxxxx") in new stack
-- Executing [s at macro-phone:1] Dial("SIP/ipkall-trunk-14838bc8",
"SIP/1651xxxxxx,25") in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
[Sep 15 14:19:34] WA...
2005 Jul 21
0
re: DTMF woes, continued
hello all,
I have a DID from nufone, transported via SIP to my * box, and even
though i'm using rfc2833 DTMF i'm still getting double digits and all
sorts of other stuff...
sip.conf is as follows:
[general]
port = 5070 ; Port to bind to
disallow=all ; Disallow all codecs
allow=ulaw
allow=alaw
allow=ilbc
allow=gsm
dtmfmode=rfc2833
register =>
2003 Aug 20
2
PRI CallerID problem
Greetings all..
We have an inbound/outbound PRI installed and terminated on a T400P ?
Digium Quad T1 card. We?re seeing an odd problem when sending
$CALLERIDNUM when calls from the PRI are forwarded back out to the PSTN
over the PRI. The $CALLERIDNUM is not being sent out along with the
call. It?s sending the phone number of the PRI itself, rather than the
$CALLERIDNUM information.
Yes, we can
2011 Jan 20
5
context problem
Hello list,
Asterisk 1.6.16.1
I have the following registrations :
register => 119909:passwd at sip.prov.org/52525252
register => 119909:passwd at sip.prov.org/59595959
[119909]
type=friend
host=sip.prov.org
username=119909
defaultuser=119909
secret=passwd
context=TRUNKin
extensions.conf :
[TRUNKin]
exten => _52525252,1,NoOp(context TRUNKin - 52525252)
exten =>
2011 Sep 02
0
No subject
crashing.
So, as a first step to solving **that** problem, make sure asterisk is
compiled with debug
flags, dumps another core file, and then you do the "gdb asterisk
<corefilename>", and
get a stack trace. That should give us some idea of what happened.
>
> I have a fairly simple Followme sequence in place to see how it works
> before I get into the complex scenarios.