- Joined
- Dec 4, 2017
- Messages
- 33
- Reaction score
- 2
Hello
We used the SIP ID option on an extension to map our 3CX extensions with our 'old' 2 digit numbers. For example, we have an extension 013 with SIP ID set to 36. This worked fine in v15.x but this night I updated to v16, and whenever anyone calls to those SIP ID, there is a 'temporarily not available' error on the phone, and the error is clearly in the logs.
So it looks like my internal SIP ID is being treated as external number, and the external number 36 obviously doesn't exist. There is also a parsebuffer, but I don't know if that actually is a result, or the cause of the problem.
Does anyone has any info on this matter?
Thanks
We used the SIP ID option on an extension to map our 3CX extensions with our 'old' 2 digit numbers. For example, we have an extension 013 with SIP ID set to 36. This worked fine in v15.x but this night I updated to v16, and whenever anyone calls to those SIP ID, there is a 'temporarily not available' error on the phone, and the error is clearly in the logs.
| 06/12/2019 10:19:05 AM - Exception: ParseException e:\jenkins\workspace\16.0\spbuild\sources\3rdparty\resiprocate\rutil\parsebuffer.hxx:230, Parse failed unexpected eof in context: 36 ^ @ e:\jenkins\workspace\16.0\spbuild\sources\3rdparty\resiprocate\rutil\parsebuffer.hxx:230 |
| 06/12/2019 10:19:05 AM - Call to T:Line:10001>>36@[Dev:sip:[email protected]2reg.be:5060] from L:7.1[Extn:002] failed, cause: Cause: 484 Address incomplete/INVITE from xxx.xxx.xxx.xxx:5060 |
So it looks like my internal SIP ID is being treated as external number, and the external number 36 obviously doesn't exist. There is also a parsebuffer, but I don't know if that actually is a result, or the cause of the problem.
Does anyone has any info on this matter?
Thanks
Last edited: