VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
aqsyounas at gmail.com Guest
|
Posted: Tue Feb 16, 2016 8:36 am Post subject: [Freeswitch-users] 400 Bad To Header. |
|
|
Hi users,
My freeswitch is replying with me 400 Bad To Header whenever It receives Bye containing this To Header.
To: 1111#15122031234 <sip:1111#15122031234@192.168.10.50:5060>;tag=NKU2jrZvFaK0j
But I wonder in the case of Invite containing, this header everything is fine.
Is there something wrong with this header? (#?)
Best regards. |
|
Back to top |
|
|
mike at jerris.com Guest
|
Posted: Tue Feb 16, 2016 10:26 am Post subject: [Freeswitch-users] 400 Bad To Header. |
|
|
I thought the # had to be encoded. Doesn't make sense that it wouldn't give you the error every time
On Tuesday, February 16, 2016, Aqs Younas <aqsyounas@gmail.com (aqsyounas@gmail.com)> wrote:
Quote: | Hi users,
My freeswitch is replying with me 400 Bad To Header whenever It receives Bye containing this To Header.
To: 1111#15122031234 <sip:1111#15122031234@192.168.10.50:5060>;tag=NKU2jrZvFaK0j
But I wonder in the case of Invite containing, this header everything is fine.
Is there something wrong with this header? (#?)
Best regards.
|
|
|
Back to top |
|
|
brian at freeswitch.org Guest
|
|
Back to top |
|
|
mike at jerris.com Guest
|
Posted: Tue Feb 16, 2016 11:03 am Post subject: [Freeswitch-users] 400 Bad To Header. |
|
|
You'll have to fix that on your device... |
|
Back to top |
|
|
aqsyounas at gmail.com Guest
|
Posted: Tue Feb 16, 2016 11:09 am Post subject: [Freeswitch-users] 400 Bad To Header. |
|
|
Much Thanks On 16-Feb-2016 9:04 pm, "Michael Jerris" <mike@jerris.com (mike@jerris.com)> wrote: |
|
Back to top |
|
|
aqsyounas at gmail.com Guest
|
Posted: Tue Feb 16, 2016 11:13 am Post subject: [Freeswitch-users] 400 Bad To Header. |
|
|
Thanks Michael,
What how can i encode this pound key? any hint is much appreciated.
Best Regards
This email has been sent from a virus-free computer protected by Avast.
www.avast.com [url=#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2][/url]
On 16 February 2016 at 20:24, Michael Jerris <mike@jerris.com (mike@jerris.com)> wrote:
|
|
Back to top |
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|