I have a problem with the forwarding of external calls.
The client has an IPECS PBX, the telephones can make internal diversions without problem.
When the phones activate the external forwarding, it doesn't work.
The scenario is the following:
Telephone number 71 You have the external diversion activated.
When they call the number XXXXXX-71, this user does not receive the call. (This extension 77 has external forwarding activated)
then I add the "ccsip messages"
Here is the message: SIP/2.0 500 Internal Server Error
Example : External Call (+49 XXXXXX14) ------> +49 xxxxx71 --> Extension 71 ( FW --> Forward to a mobile number )
----
005020: Aug 2 09:07:45.911: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:+49XXXXXXX71@tel.t-online.de:5060;transport=tcp;user=phone SIP/2.0
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
Record-Route: <sip:stat.sip-trunk.telekom.de;transport=tcp;lr>
Max-Forwards: 62
To: <sip:+49XXXXXXX71@telekom.de;user=phone>
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
Call-ID: 987c18c2009f09fd@87.137.173.231
Contact: <sip:niHuIyCRnwOs7+T6NzPmpKxZlHGeDdw5jmEbNYAV6BBw22gmwguJwqk0GvZ1clgHCxns@th1>
Supported: 199,histinfo
CSeq: 50054372 INVITE
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, PRACK, PUBLISH, REFER, REGISTER, SUBSCRIBE, UPDATE
Expires: 180
P-Asserted-Identity: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>
P-Called-Party-ID: <sip:+49XXXXXXX71@sip-trunk.telekom.de;user=phone>
Session-ID: 4b010d0b5588618076c77bca71510793;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 233
v=0
o=- 89723675773290 89723675773290 IN IP4 217.0.129.100
s=on transit
c=IN IP4 217.0.133.117
t=0 0
m=audio 20278 RTP/AVP 8 101
a=sendrecv
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
005021: Aug 2 09:07:45.919: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
To: <sip:+49XXXXXXX71@telekom.de;user=phone>
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 INVITE
Allow-Events: telephone-event
Content-Length: 0
005022: Aug 2 09:07:46.177: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
To: <sip:+49XXXXXXX71@telekom.de;user=phone>;tag=60404785-1D1C
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:+49XXXXXX10@93.241.231.36>
Contact: <sip:+49XXXXXXX71@93.241.231.36:5060;transport=tcp>
Record-Route: <sip:stat.sip-trunk.telekom.de;transport=tcp;lr>
Content-Length: 0
005023: Aug 2 09:07:46.540: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
To: <sip:+49XXXXXXX71@telekom.de;user=phone>;tag=60404785-1D1C
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:+49XXXXXX10@93.241.231.36>
Contact: <sip:+49XXXXXXX71@93.241.231.36:5060;transport=tcp>
Record-Route: <sip:stat.sip-trunk.telekom.de;transport=tcp;lr>
Content-Length: 0
005024: Aug 2 09:07:46.930: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
To: <sip:+49XXXXXXX71@telekom.de;user=phone>;tag=60404785-1D1C
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:+49XXXXXX10@93.241.231.36>
Contact: <sip:+49XXXXXXX71@93.241.231.36:5060;transport=tcp>
Record-Route: <sip:stat.sip-trunk.telekom.de;transport=tcp;lr>
Content-Length: 0
005025: Aug 2 09:07:46.963: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
To: <sip:+49XXXXXXX71@telekom.de;user=phone>;tag=60404785-1D1C
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=16
Content-Length: 0
005026: Aug 2 09:07:47.000: //7446/E134ED29973C/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:+49XXXXXX71@tel.t-online.de:5060;transport=tcp;user=phone SIP/2.0
Via: SIP/2.0/TCP 217.0.129.100:5060;branch=z9hG4bK6aeaa39b2e79308e03d144e2aef5c447.6972df8a
Max-Forwards: 62
To: <sip:+49XXXXXXX71@telekom.de;user=phone>;tag=60404785-1D1C
From: <sip:+49XXXXXXX14@sip-trunk.telekom.de;user=phone>;tag=320109bb
Call-ID: 987c18c2009f09fd@87.137.173.231
CSeq: 50054372 ACK
Content-Length: 0
---------------
