Support A2Billing :

provided by Star2Billing S.L.

Support A2Billing :
It is currently Thu Apr 18, 2024 8:43 am
Predictive Dialer


All times are UTC




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Calls are connected but ther eis no voice if go through A2B
PostPosted: Tue Feb 12, 2008 2:48 pm 
Offline

Joined: Fri Aug 31, 2007 4:01 am
Posts: 7
To whoever can suggest any ideas,

I cam across this problem and trying for hours to fix but no luck.

Here's the situation

I have asterisk 1.4.18 installed and I have a SIP provider called "provider1"
[provider1]
type=peer
host=sip.xxxxxx.com
username=0xxxxx
secret=xxxxx
qualify=yes
dtmfmode=RFC2833
canreinvite=no
sendrpid=yes
nat=yes
insecure=port,invite
disallow=all
allow=g729

When I dial out using the above trunk directly it works just fine.
e.g.
[dialout]
exten => _X.,1,Dial(SIP/provider1/${EXTEN})

When I dial using a2billing.php the two calls connected but there is just no voice/sound on both sides.
[a2billing]
exten => _X.,n,DeadAGI(a2billing.php|2)

Any ideas why?

The really strange thing is that, if I put this provider1 trunck on a different asterisk server going through the exact same provider1 via A2B and it worked.
So here are the scenarios
1) [my asterisk box 1] ==>Provider1 (this works)
2) [my asterisk box 1] ==>A2B==>Provider1 (calls connects but no sound)
3) [my asterisk box 1] ==>A2B==>[exact same Provider1 on asterisk box 2] (this works)

And I have tried three different providers and tried all the codecs availbe and still the same problems. Going through A2B the phone rings and connects but no sound.

Help please .


Top
 Profile  
 
 Post subject:
PostPosted: Tue Feb 12, 2008 4:10 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
I'm guessing this is a codec or NAT issue. You should analyse the output of the Asterisk console with 'set verbose 15' whilst placing a good and bad call. If that yields no clues try again after enabling 'sip debug'. voip-info wiki will undoubtedly provide assistance with your understanding of this and other issues.
When debugging VoIP problems it's often quicker to fire up Wireshark and analyse the call legs from the captured packets directly, rather than piecing together SIP dialogues from multiple Asterisk consoles. You will need to apply an understanding of IP, CIDR, SIP, SDP and RTP to gain any benefit from this method.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 13, 2008 8:25 am 
Offline

Joined: Fri Aug 31, 2007 4:01 am
Posts: 7
Finally, after hours of testing... a fix was found

As soon as I unload the module ip_nat_sip from the kernel. Whola! I can hear the sounds now!


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 13, 2008 9:48 am 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
Excellent news! Well diagnosed!
Of course, voip-info were not going to be easily defeated.
Is there anything Asterisk related that site doesn't document? Except A2B of course.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 
VoIP Billing solution


All times are UTC


Who is online

Users browsing this forum: No registered users and 9 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group