asterisk users - Feb 2005 - Anyone having trouble with VoicePulse Connect?

I've been using my voicepulse connect number for over
a month now, but today it simply won't connect. My
partner and I each have a number, both are mapped in
my iax.conf and extensions.conf files. This has been
working fine.

Today, either number gives this message:
Feb 16 21:53:14 NOTICE[4330]: chan_iax2.c:5757
socket_read: Rejected connect attempt from
66.234.228.170, request
'##########@voicepulse_connect_context' does not exist

where ########## is the number I dialed. Obviously
chan_iax2 knows which of the numbers I dialed, but for
some reason is unable to connect my machine to
voicepulse?

Any troubleshooting tips? This is frustrating! I
_have_ asked a question via my VoicePulse Connect web
account, but I don't know when they will respond. 

Thanks,
BeOnIce.



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

I was doing some testing and it seems to be related to
my extensions.conf. 

I have a #include <extensions_from_mysql.conf> that
was working fine yesterday:

[voicepulse_connect_context2]
exten => s,1,Answer
exten => s,2,NoOp,${CALLERID}
#include <extensions_from_mysql.conf>

and extensions_from_mysql.conf is:
[voicepulse_connect_context]
exten => 1234567890,1,VoiceMail(u1234567890)    ;
exten => 1234567890,2,Background(goodbye)()     ;
exten => 1234567890,3,Hangup()  ;
exten => 1234567890,102,VoiceMail(b1234567890)  ;
exten => 1234567890,103,Background(goodbye)()   ;
exten => 1234567890,104,Hangup()        ;

Today this _will_NOT_ work. Today, the only way I can
get it to work is to set the context in
extensions.conf back to 

[voicepulse_connect_context]

exten => s,1,Answer
exten => s,2,NoOp,${CALLERID}
; stick my extensions in here
;
;#include <extensions_from_mysql.conf>

Note that I've had to comment out the #include!

Has anyone run into this weird behaviour? I am not
convinced as to where the problem is, given that the
message still seems to indicate somehow that the
interaction with voicepulse is the problem.

Thanks,
BeOnIce.

--- beonice <beonice@yahoo.com> wrote:
> I've been using my voicepulse connect number for
> over
> a month now, but today it simply won't connect. My
> partner and I each have a number, both are mapped in
> my iax.conf and extensions.conf files. This has been
> working fine.
> 
> Today, either number gives this message:
> Feb 16 21:53:14 NOTICE[4330]: chan_iax2.c:5757
> socket_read: Rejected connect attempt from
> 66.234.228.170, request
> '##########@voicepulse_connect_context' does not
> exist
> 
> where ########## is the number I dialed. Obviously
> chan_iax2 knows which of the numbers I dialed, but
> for
> some reason is unable to connect my machine to
> voicepulse?
> 
> Any troubleshooting tips? This is frustrating! I
> _have_ asked a question via my VoicePulse Connect
> web
> account, but I don't know when they will respond. 
> 
> Thanks,
> BeOnIce.
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.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
> 


		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail

Look at an EXTENSIONS RELOAD and make sure the include is being parsed 
-- and not throwing file not found errors. I broke my include 
functionality last week by reMAKEing and not paying attention to a 
known bug in the #INCLUDE function that existed in non-HEAD versions.

/rg

On Feb 16, 2005, at 10:41 PM, beonice wrote:
> I was doing some testing and it seems to be related to
> my extensions.conf.
>
> I have a #include <extensions_from_mysql.conf> that
> was working fine yesterday: