| Summary: | ASTERISK-01827: iax2.conf type=user should be able to drive codec acceptance | ||
| Reporter: | Andrew Kohlsmith (akohlsmith) | Labels: | |
| Date Opened: | 2004-06-15 10:52:20 | Date Closed: | 2011-06-07 14:10:14 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I see that type=peer can allow and disallow codecs. I feel that type=user should be able to do this as well. My particular example. ast1 has a telco PRI attached to it with two DIDs, one for fax and one for phone. ast2 is the box at the office with a channel bank. When we send a fax, we want to negotiate ulaw. When we place a voice call, we want iLBC. Similarly when the fax DID is called we want to negotiate ulaw, and when a voice call comes in from the telco we want iLBC. so the iax.conf looks like this: disallow=all allow=ilbc allow=ulaw [ast2] type=peer host=192.168.2.1 secret=secret [phone] type=user host=192.168.2.2 secret=secret [fax] type=user host=192.168.2.2 secret=secret disallow=all allow=ulaw I've also tried with no allow=ulaw above all the entries and trying to just enable it for faxes... since it's a user the allow line just doesn't work. I can get around this by having two peers but that is messy, IMO. The peer is the same, just different users with different codec needs. | ||
| Comments: | By: Mark Spencer (markster) 2004-06-15 11:09:52 You can already specify codecs on a per-user and per-peer basis. This is a configuration issue, so you might have some luck on IRC. | ||