On Sat, Jun 15, 2013 at 04:24:21PM -0400, Andre Goree wrote:
Thanks so much for your suggestions.
I'm running 1.0.x (yes, archaic, and in fact my actual task is
migrating this system to asterisk11+Freepbx -- very fun in and of
itself without regards to this issue...but I digress), and so I
Jun 15 13:06:05 VERBOSE[30232]: -- Executing Dial(Zap/1-1,
zap/g1/1XX|20|tT) in new stack
Jun 15 13:06:05 VERBOSE[30232]: -- Called g1/1XX
Jun 15 13:06:08 VERBOSE[30232]: -- Zap/2-1 answered Zap/1-1
Jun 15 13:06:08 VERBOSE[30232]: -- Attempting native bridge of Zap/1-1
and
On Sat, Jun 15, 2013 at 2:18 PM, Daniel Tryba dan...@tryba.nl wrote:
Jun 15 13:06:05 VERBOSE[30232]: -- Executing Dial(Zap/1-1,
zap/g1/1XX|20|tT) in new stack
Jun 15 13:06:05 VERBOSE[30232]: -- Called g1/1XX
Jun 15 13:06:08 VERBOSE[30232]: -- Zap/2-1 answered Zap/1-1
Jun 15
They are either incompetant or lying to you. Call appears to succeed (it
is answered) and gets disconnected after 23s. You are not generating the
message, so the calls gets back to you telco.
Most likely someone is filtering on callerID (which is a good thing IMHO).
Set the callerid to one
On Sat, Jun 15, 2013 at 03:02:41PM -0400, Andre Goree wrote:
Setting the CID did not work, unfortunately :(
[...]
I'm going to try another number that we have through them in hopes
that it'll complete and I'll let you know if that works. Do you have
any other suggestions on what you think
On Sat, Jun 15, 2013 at 4:03 PM, Daniel Tryba dan...@tryba.nl wrote:
On Sat, Jun 15, 2013 at 03:02:41PM -0400, Andre Goree wrote:
Setting the CID did not work, unfortunately :(
[...]
I'm going to try another number that we have through them in hopes
that it'll complete and I'll let you know
Do a pri set debug (or whatever it is called in 1.4 (zap?)) Zap/Zap
bridging should work, it did on my PRIs and still does with DAHDI. Only
thing I can think of is the TON/NPI might be a problem (but doubt it
since SIP/Zap works).
Thanks so much for your suggestions.
I'm running 1.0.x
