Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
Le mardi 26 septembre 2006 à 04:17 -0400, Sick Twist a écrit : From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 09:52:21 +0200 Following the trace, only PCMA is enabled, not PCMU. Obviously. The realm, as indicated in the trace, is BroadWorks, not sip.broadvoice.com. It is not a compliant realm. snip Thanks for the reply. So are you saying that BroadVoice's SIP implementation is broken or do I have Ekiga misconfigured? I am a strong advocate for standards and if BroadVoice cannot adhere to them then perhaps I should find another provider. If you change the realm to BroadWorks in Ekiga's setup, it will work. Is there some way that Ekiga could be made to ignore the unsupported audio codecs so that a user does not need to manually disable them? It makes troubleshooting and setup much more difficult for VoIP newbies like myself. Unsupported codecs are already ignored, I do not understand what you mean. Jonathon ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone: http://www.ekiga.org/ v_/_FOSDEM 2006: http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 09:52:21 +0200 Following the trace, only PCMA is enabled, not PCMU. Obviously. The realm, as indicated in the trace, is BroadWorks, not sip.broadvoice.com. It is not a compliant realm. snip Thanks for the reply. So are you saying that BroadVoice's SIP implementation is broken or do I have Ekiga misconfigured? I am a strong advocate for standards and if BroadVoice cannot adhere to them then perhaps I should find another provider. Is there some way that Ekiga could be made to ignore the unsupported audio codecs so that a user does not need to manually disable them? It makes troubleshooting and setup much more difficult for VoIP newbies like myself. Jonathon ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
From: Jan Schampera [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Mon, 25 Sep 2006 20:25:14 +0200 On Mon, 25 Sep 2006 14:13:27 -0400 Sick Twist [EMAIL PROTECTED] wrote: Ekiga Preferences: NAT Traversal Method: None Yea, I understand. Audio Codecs: Make sure that _only_ PCMU 64 kbps 8 kHz is checked. Mh, I don't understand that one. Does the provider refuse connection when Ekiga provides more than that codec? If not, does it work when it's the first codec in the list? When I start Ekiga I can place one telephone call sucessfully. After that, Ekiga displays Security check failed when I attempt to make additional calls. Does anyone have any ideas? Thanks in advance. Uh. We would need a complete debug output of the SIP session. ekiga -d 4 Best is, you post it somewhere (pastebin.ca). The security check failed is a subsequent message from some SIP error message the provider sent. J. I'm running Ekiga on Ubuntu's development version, Edgy Eft. Ekiga was version 2.0.2 but it was just upgraded to version 2.0.3 and now I can't place any calls at all. When I try to place a call it says No common codec. When I was using Ekiga 2.0.2, I could only make calls when the PCMU codec was the only audio codec selected. If I moved PCMU to the top of the codec list but had the other codecs checked, I would get an authentication error when trying to make calls. There is definitely something strange going on with BroadVoice and the way that Ekiga announces what audio codecs are available. Here is the Ekiga 2.0.3 debug output: http://pastebin.ca/182662 ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
Le mardi 26 septembre 2006 à 04:40 -0400, Sick Twist a écrit : From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 10:25:23 +0200 If you change the realm to BroadWorks in Ekiga's setup, it will work. snip Unsupported codecs are already ignored, I do not understand what you mean. If audio codecs that are not supported by BroadVoice are enabled in Ekiga 2.0.1, the connection fails with the message Security check failed: http://pastebin.ca/182703 That can not be related. I changed the realm to BroadWorks and the only codec enabled is PCMU but it still fails in Ekiga 2.0.3: http://pastebin.ca/182700 Broadvoice clearly reports that it doesn't support PCMU. -- _ Damien Sandras (o- //\ Ekiga Softphone: http://www.ekiga.org/ v_/_FOSDEM 2006: http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
Le mardi 26 septembre 2006 à 10:26 -0400, Sick Twist a écrit : From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 12:07:28 +0200 Broadvoice clearly reports that it doesn't support PCMU. -- If PCMU is another name for G.711u then BroadVoice does support it. Plus, I have seen both Ekiga version 2.0.1 and 2.0.2 make calls via BroadVoice with PCMU enabled. Ekiga 2.0.3 has a regression that causes it to display No common codec with the same settings that I use with Ekiga version 2.0.1 and 2.0.2. I'm really sorry, but unfortunately that's wrong. If you look at the trace, you can see this : INVITE sip:[EMAIL PROTECTED] SIP/2.0 Route: sip:proxy.mia.broadvoice.com:5060;lr Date: Tue, 26 Sep 2006 08:28:10 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.1.117:5063;branch=z9hG4bKf05bb69c-a64b-db11-804a-000d60f993e4;rport User-Agent: Ekiga/2.0.3 From: Jonathon Conte sip:[EMAIL PROTECTED];tag=4054af9c-a64b-db11-804a-000d60f993e4 Call-ID: [EMAIL PROTECTED] To: sip:[EMAIL PROTECTED] Contact: sip:[EMAIL PROTECTED]:5063;transport=udp Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 255 Max-Forwards: 70 v=0 o=- 1159259290 1159259290 IN IP4 192.168.1.117 s=Opal SIP Session c=IN IP4 192.168.1.117 t=0 0 m=audio 5000 RTP/AVP 101 0 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:0 PCMU/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/9 And Broadvoice answers with this : SIP/2.0 415 Unsupported Media Type CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.1.117:5063;branch=z9hG4bKf05bb69c-a64b-db11-804a-000d60f993e4;received=72.40.109.121;rport=15063 From: Jonathon Conte sip:[EMAIL PROTECTED];tag=4054af9c-a64b-db11-804a-000d60f993e4 Call-ID: [EMAIL PROTECTED] To: sip:[EMAIL PROTECTED] Content-Length: 0 Ekiga has no control over what Broadvoice sends back and I have no idea what could cause the Unsupported Media Type message. You should perhaps try without video support. -- _ Damien Sandras (o- //\ Ekiga Softphone: http://www.ekiga.org/ v_/_FOSDEM 2006: http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 18:13:55 +0200 snip Ekiga has no control over what Broadvoice sends back and I have no idea what could cause the Unsupported Media Type message. You should perhaps try without video support. -- That fixed it. Thank you so much! Jonathon ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
Le mardi 26 septembre 2006 à 12:57 -0400, Sick Twist a écrit : From: Damien Sandras [EMAIL PROTECTED] Reply-To: Ekiga mailing list ekiga-list@gnome.org To: Ekiga mailing list ekiga-list@gnome.org Subject: Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice Date: Tue, 26 Sep 2006 18:13:55 +0200 snip Ekiga has no control over what Broadvoice sends back and I have no idea what could cause the Unsupported Media Type message. You should perhaps try without video support. -- That fixed it. Thank you so much! Excellent! I would really not have thought that it could cause the problem, but I'm happy it is now fixed! -- _ Damien Sandras (o- //\ Ekiga Softphone: http://www.ekiga.org/ v_/_FOSDEM 2006: http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Trouble setting up Ekiga for BroadVoice
On Mon, 25 Sep 2006 14:13:27 -0400 Sick Twist [EMAIL PROTECTED] wrote: Ekiga Preferences: NAT Traversal Method: None Yea, I understand. Audio Codecs: Make sure that _only_ PCMU 64 kbps 8 kHz is checked. Mh, I don't understand that one. Does the provider refuse connection when Ekiga provides more than that codec? If not, does it work when it's the first codec in the list? When I start Ekiga I can place one telephone call sucessfully. After that, Ekiga displays Security check failed when I attempt to make additional calls. Does anyone have any ideas? Thanks in advance. Uh. We would need a complete debug output of the SIP session. ekiga -d 4 Best is, you post it somewhere (pastebin.ca). The security check failed is a subsequent message from some SIP error message the provider sent. J. -- Der Mensch, der bereit ist, seine Freiheit aufzugeben, um Sicherheit zu gewinnen, wird beides verlieren. - Benjamin Franklin ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
