[VoiceOps] Possible Windstream - Broadsoft misconfiguration?

[Mark Wiles]

Hey all,

Anyone on here that's part of Windstream's Broadsoft deployment group?

We're running into a problem where it appears there could be a
misconfiguration on a switch.

In the initial INVITE message we're receiving, the Diversion header contains
the To number - and this is causing our Metaswitch some heartburn in some
specific cases (not to our customers).

Any assist would be greatly appreciated!

Mark

 

 

INVITE sip:+1706288XXXX at xxx.xxx.xxx.xxx:5060 SIP/2.0
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK00B105cb36f4579bb83
From: "ABC" <sip:+1803279XXXX at xxx.xxx.xxx.xxx>;tag=gK00200ada
To: <sip: <sip:706288XXXX at xxx.xxx.xxx.xxx> 706288XXXX at xxx.xxx.xxx.xxx>
Call-ID: 1191215837_100642076 at xxx.xxx.xxx.xxx
<mailto:1191215837_100642076 at xxx.xxx.xxx.xxx> 
CSeq: 866803 INVITE
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS
Accept: application/sdp
Contact: "ABC" <sip:+1803279XXXX at xxx.xxx.xxx.xxx:5060>
P-Asserted-Identity: "ABC" <sip:+1803279XXXX at xxx.xxx.xxx.xxx:5060>
Diversion: <sip:+1706288XXXX at xxx.xxx.xxx.xxx:5060>;privacy=off;screen=no;
reason=unconditional; counter=1
Supported: replaces
Content-Length:   281
Content-Disposition: session; handling=required
Content-Type: application/sdp

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170921/4083d12b/attachment.html>