"Bearer capability not implemented" Error on incoming calls.
connection terminated directly to VM. and rings the SPA-3102 ATA. no incoming calls go thru. Out going works. FPL softphone. no ring and no connection.
Bearer capability not implemented.
-
KevinBroten
- Just Passing Thru
- Posts: 2
- Joined: 10/09/2011
- SIP Device Name: CISCO SPA-3102
- Firmware Version: 5.1.10(GW)
- ISP Name: Teksavvy
- Computer OS: windows 7
- Router: DIR-815
-
tbrummell
- Tried and True
- Posts: 330
- Joined: 09/21/2010
- SIP Device Name: PIAF/Mitel/PolyCom/Cisco
- Firmware Version: Asterisk 1.8
- ISP Name: Rogers
- Computer OS: CentOS/Windows2008/Win7/Android
- Router: pfSense/Neoware thin client
- Location: Ottawa
Re: Bearer capability not implemented.
A little more information would be great, and full sentences with punctuation would help too.
Is the caller hearing said message? Is it appearing in a log somewhere? You're saying the FPL softphone does not work at all, yet your ATA can get outbound calls through? This is confusing, "connection terminated directly to VM. rings the SPA-3102". You are contradicting yourself. The call is going directly to VM *and* ringing the ATA? If there are logs for this, please post them using Code tags.
What codecs are enabled in the SPA, and in what order are they set to be used (I'm not sure it's possible to prioritize codecs in the 3102, I've never used one)? FPL supports 729 and 711u, try with just those 2 codecs enabled. "Bearer capability not implemented" is typically a carrier related error on ISDN links.
As for the softphone, it appears YMMV is in play with it, works for some folks, doesn't work for others. I never did get it working properly on Win7 and haven't tried it in the past year at all. Maybe things have improved with it, but it doesn't sound like it.
Is the caller hearing said message? Is it appearing in a log somewhere? You're saying the FPL softphone does not work at all, yet your ATA can get outbound calls through? This is confusing, "connection terminated directly to VM. rings the SPA-3102". You are contradicting yourself. The call is going directly to VM *and* ringing the ATA? If there are logs for this, please post them using Code tags.
What codecs are enabled in the SPA, and in what order are they set to be used (I'm not sure it's possible to prioritize codecs in the 3102, I've never used one)? FPL supports 729 and 711u, try with just those 2 codecs enabled. "Bearer capability not implemented" is typically a carrier related error on ISDN links.
As for the softphone, it appears YMMV is in play with it, works for some folks, doesn't work for others. I never did get it working properly on Win7 and haven't tried it in the past year at all. Maybe things have improved with it, but it doesn't sound like it.
-
KevinBroten
- Just Passing Thru
- Posts: 2
- Joined: 10/09/2011
- SIP Device Name: CISCO SPA-3102
- Firmware Version: 5.1.10(GW)
- ISP Name: Teksavvy
- Computer OS: windows 7
- Router: DIR-815
Re: Bearer capability not implemented.
"Bearer capability not implemented" is listed in the logs for the failed phone calls on FPL's call log page. Possible that the source caller telecom is not compatible setting wise with FPL's system?
and yes the Voice mail is presented to the caller. yet at the same time the ATA receives a ring-in. and gets a rings pattern briefly. I know it's contradictory, that is what is confusing. The ATA does not connect to the incoming call. 711u and 729 are turned on for the line.
Update: I now can receive a call from the same number. settings are same as when not connecting.
and yes the Voice mail is presented to the caller. yet at the same time the ATA receives a ring-in. and gets a rings pattern briefly. I know it's contradictory, that is what is confusing. The ATA does not connect to the incoming call. 711u and 729 are turned on for the line.
Update: I now can receive a call from the same number. settings are same as when not connecting.