Hello
Astpp version 6, how enable ipv6?
Do I just need to create a new profile with IPv6, or is there something else that needs to be done?
Yes, it needs its own profile
I created and registered it, but it fails when passing calls.
I copied everything from the IPv4 profile, but it doesn’t work. Do I need to change something else?
2026-01-30 15:28:06.596001 99.10% [DEBUG] switch_core_media.c:8660 AUDIO RTP [sofia/ASTPPIPV6/Myaccount@MyIPV6] IPV6 port 19200 → IPV6_Account port 10600 codec: 18 ms: 20
2026-01-30 15:28:06.596001 99.10% [DEBUG] switch_core_media.c:8973 sofia/ASTPPIPV6/Myaccount@MyIPV6 Set 2833 dtmf send payload to 101
2026-01-30 15:28:06.596001 99.10% [DEBUG] switch_core_media.c:8980 sofia/ASTPPIPV6/Myaccount@MyIPV6 Set 2833 dtmf receive payload to 101
2026-01-30 15:28:06.596001 99.10% [DEBUG] switch_core_media.c:9003 sofia/ASTPPIPV6/Myaccount@MyIPV6 Set rtp dtmf delay to 40
2026-01-30 15:28:06.596001 99.10% [NOTICE] mod_sofia.c:2610 Pre-Answer sofia/ASTPPIPV6/Myaccount@MyIPV6!
2026-01-30 15:28:06.596001 99.10% [DEBUG] switch_channel.c:3585 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Callstate Change RINGING → EARLY
2026-01-30 15:28:06.615999 99.10% [DEBUG] sofia.c:7493 Channel sofia/ASTPPIPV6/Myaccount@MyIPV6 entering state [early][183]
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_ivr_bridge.c:819 sofia/ASTPPIPV6/Myaccount@MyIPV6 ending bridge by request from write function
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_ivr_bridge.c:911 BRIDGE THREAD DONE [sofia/ASTPPIPV6/Myaccount@MyIPV6]
2026-01-30 15:28:06.735999 99.10% [NOTICE] switch_core_state_machine.c:382 sofia/ASTPPIPV6/Myaccount@MyIPV6 has executed the last dialplan instruction, hanging up.
2026-01-30 15:28:06.735999 99.10% [NOTICE] switch_core_state_machine.c:384 Hangup sofia/ASTPPIPV6/Myaccount@MyIPV6 [CS_EXECUTE] [NORMAL_CLEARING]
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:647 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State EXECUTE going to sleep
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:581 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Running State Change CS_HANGUP (Cur 20 Tot 787)
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:844 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Callstate Change EARLY → HANGUP
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:846 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State HANGUP
2026-01-30 15:28:06.735999 99.10% [DEBUG] mod_sofia.c:469 Channel sofia/ASTPPIPV6/Myaccount@MyIPV6 hanging up, cause: NORMAL_CLEARING
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:59 sofia/ASTPPIPV6/Myaccount@MyIPV6 Standard HANGUP, cause: NORMAL_CLEARING
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:846 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State HANGUP going to sleep
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:616 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State Change CS_HANGUP → CS_REPORTING
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:581 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Running State Change CS_REPORTING (Cur 20 Tot 787)
2026-01-30 15:28:06.735999 99.10% [DEBUG] switch_core_state_machine.c:932 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State REPORTING
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:168 sofia/ASTPPIPV6/Myaccount@MyIPV6 Standard REPORTING, cause: NORMAL_CLEARING
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:932 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State REPORTING going to sleep
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:607 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State Change CS_REPORTING → CS_DESTROY
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_session.c:1744 Session 782 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Locked, Waiting on external entities
2026-01-30 15:28:06.756001 99.10% [NOTICE] switch_core_session.c:1762 Session 782 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Ended
2026-01-30 15:28:06.756001 99.10% [NOTICE] switch_core_session.c:1766 Close Channel sofia/ASTPPIPV6/Myaccount@MyIPV6 [CS_DESTROY]
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:735 (sofia/ASTPPIPV6/Myaccount@MyIPV6) Running State Change CS_DESTROY (Cur 18 Tot 787)
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:745 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State DESTROY
2026-01-30 15:28:06.756001 99.10% [DEBUG] mod_sofia.c:380 sofia/ASTPPIPV6/Myaccount@MyIPV6 SOFIA DESTROY
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:175 sofia/ASTPPIPV6/Myaccount@MyIPV6 Standard DESTROY
2026-01-30 15:28:06.756001 99.10% [DEBUG] switch_core_state_machine.c:745 (sofia/ASTPPIPV6/Myaccount@MyIPV6) State DESTROY going to sleep
Does anyone have any suggestions???
you may want to try using sngrep to see what is going on
@rgazetta did you manage to get that working?
Your IPv6 profile is working correctly at the SIP and RTP level. The call is reaching EARLY state (183), which means the connection and media negotiation are happening successfully. The real issue is this line:
“has executed the last dialplan instruction, hanging up”
This means the dialplan is completing without a bridge instruction, so the call drops. This is a routing configuration issue rather than an IPv6 problem specifically.
A few things to check:
First, in your outbound routes, confirm the gateway assigned is your IPv6 gateway and not the IPv4 one. Copying the profile does not automatically copy the routing assignments.
Second, check the dialplan context for the IPv6 profile and make sure there is a valid bridge target configured after the call connects.
Third, run sngrep as suggested and watch where the call is being sent after the 183. It will quickly confirm whether the destination is resolving correctly over IPv6.
If you can share your outbound route setup and gateway configuration for the IPv6 profile along with freeswitch full call log, we can help you pinpoint it from there.
1 Like