| Summary: | ASTERISK-00086: iax.conf to SIP call bug | ||
| Reporter: | eanders (eanders) | Labels: | |
| Date Opened: | 2003-08-12 12:37:40 | Date Closed: | 2011-06-07 14:04:56 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | [11:29] <erik> Kram, I really need a pointer. [11:29] <erik> Cisco 7960 question. When I dial my SIP Cisco 7960 through Asterisk local LAN it works. When I try and IAX from another asterisk system to my asterisk->Cisco I get a [11:30] <erik> -- Got SIP response 400 "Bad Request" back from 192.168.1.112 [11:30] <erik> 192.168.1.112 being my Cisco 7960 [11:30] <kram> take the sip debug and post a bug in the bug tracker [11:30] <erik> I have converted my Cisco to SIP versus skinny [11:31] <kram> or you can e-mail me the trace [11:31] <erik> Ok. email addr? [11:34] <kram> markster@digium.com [12:07] <erik> Mark, I found the Bug. If in the iax.conf file I have [12:07] <erik> callerid="Guest IAX User" [12:08] <erik> The "" will end up breaking the SIP call [12:08] <erik> Because the From field looks like [12:08] <erik> From ""Guest IAX User"" <yadda yadda> [12:08] <erik> I sent you an email on this [12:09] <erik> I ran just ran ethereal on my Asterisk server and the problem showed itself I ran ethereal on my Asterisk box and the problem showed itself. iax.conf [guest] type=friend context=default allow=g729 allow=iLBC allow=gsm callerid="Guest IAX User" As noted above the "" in the callerid field will break a SIP call because the SIP From field in the Request/Invite field will be From: ""Guest IAX User"" When I changed callerid to callerid=Guest IAX User It worked fine. | ||
| Comments: | By: John Todd (jtodd) 2003-09-08 21:11:37 Is this still broken? eanders, can you test again? I seem to recall someone talking about a fix to this a while back, but I am uncertain if it was implemented. By: John Todd (jtodd) 2003-10-19 20:15:03 No activity on this from bug reporter in more than a month. Marking as resolved. | ||