.
If anyone has an idea, I've included the related configs and the trace of a
call.
Best regards,
Nicolas Olivier
The gateway is running asterisk 1.0.7.
sip.conf:
[general]
context=default
port=5060
bindaddr=yyy.yyy.yyy.yyy
srvlookup=yes
[provider]
type=friend
host=zzz.zzz.zzz.zzz
port=5060
nat=yes
.
If anyone has an idea, I've included the related configs and the trace of a
call.
Best regards,
Nicolas Olivier
The gateway is running asterisk 1.0.7.
sip.conf:
[general]
context=default
port=5060
bindaddr=yyy.yyy.yyy.yyy
srvlookup=yes
[provider]
type=friend
host=zzz.zzz.zzz.zzz
port=5060
nat=yes
This is the information I got from Swissvoice support, I didn't tried yet, but
if it can helps.
How to use an external phone book
IP10S phone supports access to Cisco Phone Book but not all functionalities.
The IP10 uses his own interface to access to the Phone Book.
If you want to connect
is known to work. I've searched
in the archives, wiki, and can't see what's wrong.
If anyone has an advice, it will be greatly appreciated.
Nicolas Olivier
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman
Just an update, I deoopsed the kernel dump, must be usable...
Nicolas Olivier wrote:
Hi,
I'm trying to setup a small BRI ISDN - voip gateway.
The ISDN card is based on Cologne chipset, so I try set it up with zaphfc.
The versions i'm running:
kernel-2.4.27
Asterisk 1.0.7-BRIstuffed
daemon.crit klogd: zaphfc[0]: b channel buffer overflow:
436, 436
May 18 18:11:33 gw-ss daemon.crit klogd: zaphfc[0]: b channel buffer underrun:
0, 0
And when I start asterisk, same stuff, kernel crashes.
Interrupts are ok.
sjaak imap wrote:
Dear Nicolas Olivier
Just try the florz patch at http
Quoting from:
http://www.voip-info.org/tiki-index.php?page=Asterisk%20Zaptel%20Installation
As I haven't got a Digium card, I need a timer which can be provided by
ztdummy, zaprtc or zaprai.
But anyway the results are the same with or without zaprtc loaded.
Peer Oliver Schmidt wrote:
Nicolas
the symptoms you are seeing are all but
identical to the issues I saw and resolved by changing out the
motherboard memory. The system was an ASUS main board with a Xeon
processor.
It is not the memory it could be something specific to the VIA motherboard.
Stuart
Nicolas Olivier wrote
