I have a peculiar scenario, maybe you guys have an easy solution:
1. a call comes in through an SBC (which is also kamailio) 2. SBC passes call to core kamailio server 3. call reaches 180 ringing state 4. client suddenly changes from wifi to 4G (using 4G IP, VIA headers are all updated) 5. client sends cancel and receives cancelling msg from SBC 6. SBC sends cancel to kamailio core 7. kamailio core sends back Request Terminated after termination the issue is, this message was sent to the wifi IP not the 4G
when checking the network dumps, looks like this was because the INVITE was received on kamailio core from the old wifi IP. Is there maybe a way to update the transaction perhaps?
Kelvin Chua
Unfortunately, calls can be set up between two fixed endpoints only. If those endpoints change, not much you can do.
I think this is a problem that some of the standards around IPv6 mobile roaming are meant to solve.
On Wed, Dec 14, 2016 at 05:51:03PM +0800, Kelvin Chua wrote:
I have a peculiar scenario, maybe you guys have an easy solution:
- a call comes in through an SBC (which is also kamailio)
- SBC passes call to core kamailio server
- call reaches 180 ringing state
- client suddenly changes from wifi to 4G (using 4G IP, VIA headers are
all updated) 5. client sends cancel and receives cancelling msg from SBC 6. SBC sends cancel to kamailio core 7. kamailio core sends back Request Terminated after termination the issue is, this message was sent to the wifi IP not the 4G
when checking the network dumps, looks like this was because the INVITE was received on kamailio core from the old wifi IP. Is there maybe a way to update the transaction perhaps?
Kelvin Chua
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
thanks for the insights alex :)
Kelvin Chua
On Wed, Dec 14, 2016 at 6:06 PM, Alex Balashov abalashov@evaristesys.com wrote:
Unfortunately, calls can be set up between two fixed endpoints only. If those endpoints change, not much you can do.
I think this is a problem that some of the standards around IPv6 mobile roaming are meant to solve.
On Wed, Dec 14, 2016 at 05:51:03PM +0800, Kelvin Chua wrote:
I have a peculiar scenario, maybe you guys have an easy solution:
- a call comes in through an SBC (which is also kamailio)
- SBC passes call to core kamailio server
- call reaches 180 ringing state
- client suddenly changes from wifi to 4G (using 4G IP, VIA headers are
all updated) 5. client sends cancel and receives cancelling msg from SBC 6. SBC sends cancel to kamailio core 7. kamailio core sends back Request Terminated after termination the issue is, this message was sent to the wifi IP not the 4G
when checking the network dumps, looks like this was because the INVITE
was
received on kamailio core from the old wifi IP. Is there maybe a way to update the transaction perhaps?
Kelvin Chua
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Kelvin Chua