Displaying 4 results from an estimated 4 matches for "031210a".
Did you mean:
0.1210
2004 Jan 12
4
RFC3389 messages with ATA 186
I'm getting some warnings:
NOTICE[xxx]: File rtp.c, Line 264 (process_rfc3389): RFC3389 support
incomplete. Turn off on client if possible
Asterisk Version: CVS-01/06/04-13:50:26
Cisco ATA 186 version: v3.0.0 atasip (Build 031210A)
Is this something I should be concerned about? Anyone know how to "turn
off" the RFC3389 support on the ata 186?
Thanks!
2004 Apr 26
0
Record-route Issues
...9931211@proxy.abccorp.net>;tag=1841513983
Call-ID: 58d4bd4e5e29ff254db520665915ac83@xxx.yyy.77.23
CSeq: 102 INVITE
Contact: <sip:xxx9931211@xxx.yyy.165.201:5060;user=phone;transport=udp>
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER
Server: Cisco ATA 186 v3.0.0 atasip (031210A)
Content-Type: application/sdp
Content-Length: 205
v=0
o=xxx9931211 18172 18172 IN IP4 xxx.yyy.165.201
s=ATA186 Call
c=IN IP4 xxx.yyy.165.201
t=0 0
m=audio 16384 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
-----------------------------------------------...
2004 Jan 18
2
Asterisk as SIP Redirect Server -- Implemented - Not Working - Plz Help
I have coded chan_sip.c so that you can have
// sip.conf
register => username:password@somedomain.com/redirectconfig
[redirectconfig]
redirect=yes
redirecturi=sip:12345@domain1.com
redirecturi=sip:34556@domain2.com
redirecturi=sip:87877@domain3.com ....
so when you receive a call it will redirect to the alternating uri's with a
SIP 300 Message.
It works with the following sequence,
2004 May 22
14
Caller ID with BT CD50
Hi All,
Having searched the archives, I can see there has been much discussion
at various points regarding capture of caller id information from good
old BT.
If I understand correctly, it seems that not only do the drivers not
currently support it, but my X101P possibly/probably can't do it anyway
due to hardware?
So, that leaves me with the modem route, which seems more and more
unlikely,